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: If i will enable module 'perl-DBD-SQLite' there is always in 'yum list-sec' multiple times 'RHBA-2019:3337' which is not applicable.
Version-Release number of selected component (if applicable):
# rpm -qa | grep -e yum -e dnf
python3-dnf-4.2.7-7.el8_1.noarch
python3-dnf-plugins-core-4.0.8-3.el8.noarch
dnf-plugins-core-4.0.8-3.el8.noarch
dnf-data-4.2.7-7.el8_1.noarch
dnf-4.2.7-7.el8_1.noarch
dnf-plugin-subscription-manager-1.25.17-1.el8.x86_64
dnf-plugin-spacewalk-2.8.5-11.module+el8.1.0+3455+3ddf2832.noarch
yum-4.2.7-7.el8_1.noarch
python3-dnf-plugin-spacewalk-2.8.5-11.module+el8.1.0+3455+3ddf2832.noarch
libdnf-0.35.1-9.el8_1.x86_64
python3-libdnf-0.35.1-9.el8_1.x86_64
How reproducible: Always
Steps to Reproduce:
1. yum module enable perl-DBD-SQLite
2. yum list-sec
3. yum update --advisory=RHBA-2019:3337
Actual results:
# yum update --advisory=RHBA-2019:3337
Failed to set locale, defaulting to C.UTF-8
Updating Subscription Management repositories.
Red Hat Satellite Tools 6.5 for RHEL 8 x86_64 (RPMs) 13 kB/s | 2.1 kB 00:00
Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 11 kB/s | 2.8 kB 00:00
Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs) 13 kB/s | 2.4 kB 00:00
No security updates needed, but 50 updates available
Dependencies resolved.
Nothing to do. <<<<<<<<<<<<<<<<<<<<
Complete!
Expected results:
Apply errata or even better not show it in list-sec
Additional info:
If i disable module this errata disappear again.
The problem is triggered by unique structure of RHBA-2019:3337 advisory.In past all advisories have a single section <pkglist> with only one <collection> inside. With modules in section <collection> information about modules <module> appeared to specify if advissory is applicable.
But from 77 modular advisories 3 advisories have a different structure. They have multiple <collection> (RHBA-2019:3337 with 15 collections, RHBA-2020:0347 with 2 collections, RHBA-2019:3416 with 2 collections) in <pkglist> and each collection have different modules there. It means that we are not talking about applicability of advisory but about applicability of collection and only packages described in that collection.
The present structure in libsolv puts all packages from advisory into a single list and all modules described in advisory also in list. Then there is no relation between modules and collection and package and collection.
There are only two ways how to resolve the issue and both are very painful. Make new structure inside libsolv => incompatible change or change generation of advisory.
Additionally - even after resolvement of this issue false positive detection of advisory will be still present in multicontext modules due data redundancy in advisory.
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 (Moderate: dnf security and bug fix 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/RHSA-2021:4464