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.

We currently remove the multilibs in %post, but we could do this earlier, in %pre. This is related to bug 2119304.

With the removal in %post, we have this issue: /lib64/glibc-hwcaps comes before /lib64/ld*, so RPM upgrades to the new version of libc.so.6 before ld.so. This means there is a window during the upgrade where new processes run with new libc.so.6 and old ld.so.

Without multilibs, /lib64/ld* comes before /lib64/lib*, and the possible race/version mismatch involves an old libc.so.6 with a new ld.so. Empirically, it is easier to evolve the GLIBC_PRIVATE ABI to better support this mismatch, so we should align the multilib case to this. This improves the upgrade experience at the expense of the downgrade experiences (but of course updates are more common because there has to be an upgrade before there can be a downgrade).

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 (glibc 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:2481