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.
From email:
* Sergey Kolosov:
> The second test fails on /install /update /downgrade /remove phases,
> because it can't install(update/downgrade/remove) glibc-headers-s390-
> 0:2.33-5.el9.noarch because of conflicted files between glibc-headers-
> s390 and glibc-headers-x86 [2] I guess glibc-headers-s390 can't be
> installed in same time with glibc-headers-x86, so should I reach #osci
> to fix osci.brew-build.installability.functional test?
Hmm. This came up recently here:
<https://pagure.io/releng/issue/8337#comment-713404>
The side effects from those noarch packages are quite bad as well.
Someone needs to follow up with Kevin Fenzi and Lubomír Sedlář to check
if the infrastructure issues we were trying to work around have been
fixed, than we can revert this construct on the glibc side [in Fedora[.
In RHEL 9, we never saw these issues, so we can do this change downstream
after inheritance from Fedora 34 has stopped, in CentOS Stream 9.
This way, the second problem should go away in early April.