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.
Hi Panu,
one thing that confuses me is that the bug 1690414 is filed against dnf on RHEL-8 while bug 1660232 is filed against rpm on RHEL-7.
Could you please clarify what are the right packages to address the issue and if that would be both in yum/dnf and rpm?
Also, is there a way how to verify (functionally) the fix made solely on rpm side? Would that prevent yum/dnf from segfaulting or a different test is needed?
This is a somewhat confusing bug as several different packages are involved with different failure characteristics on each.
In a sense, this could be addressed on just dnf/yum side, or rpm. But there are flaws on both sides, so its better to cover both as it's possible those flaws could be reached through other means as well.
On rpm we need to avoid a NULL pointer in a specific place, that's bug 1698850 and bug 1660232 for RHEL-8 and RHEL-7 respectively. Both dnf and yum need essentially the same fix for test-transaction return code checking to cover other similar non-package oriented errors that might occur in the (test-)transaction.
Rpm itself cannot directly reproduce the issue, but yes the rpm-side fix will prevent the segfault in both dnf and yum, so the same test (using unfixed dnf/yum) can be used to test it.
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, 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-2019:3583