RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When upgrading a package that has an "optional" dependency on another package using the "Conflicts: package < version" directive, yum does not guarantee that that the other package is updated first.

This causes issues with packages that are trying to mandate an SELinux update if an SELinux denial would result in the package not starting properly.

For example:
Upgrading SSSD from RHEL 6.1 to RHEL 6.2 added a dependency on selinux-policy 3.7.19-118

To do this (since it must be possible to run SSSD with no SELinux packages on the system, we added:
Conflicts: selinux-policy < 3.7.19-118

When SSSD upgrades, it restarts its daemon (if it's currently running). The new version of this package required the newer selinux policy to grant a new permission to allow it to start up. The end result was that SSSD was not running after an upgrade.

Yum should be modified so that conditional Conflicts: are resolved before dependent packages are updated.


Version-Release number of selected component (if applicable):
https://brewweb.devel.redhat.com/buildinfo?buildID=183779

How reproducible:
Inconsistent. Order is not guaranteed

Steps to Reproduce:
See description

Transaction ordering is part of rpm, and I'm kind of surprised that this doesn't already happen ... are you sure there aren't any loops in the deps?

I can guarantee you that selinux-policy does not depend on SSSD, so there are no loops.

*** This bug has been marked as a duplicate of bug 760793 ***