Using update for errata install via Remote Execution instead of update-minimal
Description of problem:
Currently errata installation via REX is using 'yum update --advisories'.
This command will update to newer packages than what was specified in the errata if newer ones are available.
For example, if a client has 'foo-1.0' installed and errata A has 'foo-2.0', but there also exists foo-3.0 in the repo, performing an errata install with REX will cause yum to pull in foo-3.0 even though foo-2.0 is in the Errata.
Yum provides an update-minimal command which provides this functionality.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Using rex try to apply an errata to a client where there is a newer version of one of the packages in the errata available via the email
Newer package is installed that is not in the errata
Older version of package that is in the errata
Satellite 5 & 6 have used similar behavior to update-minimal for many years
in RHEL 7.0 and 7.1 there is a known bug: https://bugzilla.redhat.com/show_bug.cgi?id=1192239
Which should be fixed in 7.2 Unsure if this complicates the matter.
#3 Updated by Adam Ruzicka over 4 years ago
- Project changed from Foreman Remote Execution to Katello
- Subject changed from Remote Execution using update for errata install instead of update-minimal to Using update for errata install via Remote Execution instead of update-minimal
Changing the project to make theforeman-bot happy