Project

General

Profile

Actions

Bug #17513

closed

Using update for errata install via Remote Execution instead of update-minimal

Added by Adam Ruzicka almost 8 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1333181

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):
6.2.0 Beta

How reproducible:
Always

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

Actual results:
Newer package is installed that is not in the errata

Expected results:
Older version of package that is in the errata

Additional info:

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.

Actions

Also available in: Atom PDF