Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
We have locked our packages down using a versionlock list, which we use to baseline a large selection of our hosts. This list is distributed and used to upgrade the hosts to the correct baseline.
Since generating the baseline, some of the packages have received minor bumps, and due to the way the minor bump version is noted, this is causing the versionlock wildcard to recognize the package, and update the rpm despite it being in the versionlock.
Example:
sssd package locked in version lock file at version 2.6.2-4.el8_6.x86_64
Written in versionlock file as: 2.6.2-4.el8_6.*
New minor bump version released: 2.6.2-4.1.el8_6.x86_64
Written down in rpm/repolist as 2.6.2-4.el8_6.1.x86_64
When we deploy our baselined versionlock file to a new host and run the yum update, it fails due to dependency issues. This is due to it trying to pull in the 2.6.2-4.el8_6.1.x86_64 version of sssd and its dependencies as they match the wildcard: 2.6.2-4.el8_6.*.
This is a bug that needs fixing, and we believe has already been fixed elsewhere. If you look at this rpm commit, this exact issue has been fixed, except for Fedora: https://github.com/rpm-software-management/dnf-plugins-core/commit/89403c17a04ac8157e02efe271c08a18c2805308
Please can this commit be pulled into the latest version of DNF on RedHat 8 (and also 6, 7, and 9 as they are also affected), so we can continue using our baselined versionlock files as expected?
What is the business impact? Please also provide timeframe information.
Each time we wish to bring a host up to the versionlock baseline, we are having to unpick dependency issues. 1-2 hours per host.
Version-Release number of selected component (if applicable):
customer environment. On RedHat 6, 7, 8, 9
dnf-4.7.0-11.el8.noarch.rpm
Actual results:
Each time we wish to bring a host up to the version lock baseline, we are having to unpick dependency issues. 1-2 hours per host.
Expected results:
It should work as expected as per the upstream
Additional info:
Every time there is a minor bump in the version to a package that is version locked with a wildcard.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (dnf-plugins-core bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:7125