Scenarios where version-locking feature can be used.

[jameerpathan111]

Version locking feature is there to protect Foreman installation from breakages caused by unwanted upgrades of the related rpm packages. The feature locks selected packages using yum versionlock plugin. As a result the unlocked system packages can be freely updated and the system can keep up with the security updates.

Upstream doc: Version locking of Foreman packages

• For Satellite 6.6+ the version-locking feature will be enabled by default.
• For previous Satellite versions, users will have option to do packages lock/unlock manually using foreman-maintain >= v0.4.2

We need to test following scenarios:

• For Satellite >= 6.6 upgrade(without using FM/manual upgrade):
  • unlock packages before yum update using foreman-installer --no-lock-package-versions or foreman-maintain packages unlock
• For Satellite >= 6.6 upgrade(using FM):
  • No changes are needed in job, foreman-maintain will unlock packages before yum update.
• For Satellite < 6.6 upgrade(without using FM):
  • User have locked packages using FM, then first unlock them using FM before updating packages.
  • This scenario is added in testfm. Add scenarios to test version-locking feature of FM testfm#69
• For Satellite < 6.6 upgrade(using FM):
  • User have locked packages using FM, then he don't need to do anything while doing upgrade using FM. FM will unlock packages before updating packages.
  • Lock package manually before performing update using FM.
• General working of version-locking feature is being tested using testfm Add scenarios to test version-locking feature of FM testfm#69.

[jameerpathan111]

Satellite upgrade done without using FM are not supported.