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.
Bug 2021809 - gcc and python3 dependencies broken
Summary: gcc and python3 dependencies broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: distribution
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Brian Stinson
QA Contact: Brian Stinson
URL:
Whiteboard:
Depends On:
Blocks: 2046690
TreeView+ depends on / blocked
 
Reported: 2021-11-10 09:24 UTC by Sandro Bonazzola
Modified: 2022-09-28 16:02 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-28 16:01:53 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-102353 0 None None None 2021-11-10 16:23:50 UTC

Description Sandro Bonazzola 2021-11-10 09:24:25 UTC 
Looks like something broke the CentOS Stream 9 repos:

DEBUG util.py:444:  Error: 
DEBUG util.py:444:   Problem 1: cannot install the best candidate for the job
DEBUG util.py:444:    - nothing provides libstdc++ = 11.2.1-6.el9 needed by gcc-c++-11.2.1-6.el9.x86_64
DEBUG util.py:444:   Problem 2: cannot install the best candidate for the job
DEBUG util.py:444:    - nothing provides libgcc >= 11.2.1-6.el9 needed by gcc-11.2.1-6.el9.x86_64
DEBUG util.py:444:    - nothing provides libgomp = 11.2.1-6.el9 needed by gcc-11.2.1-6.el9.x86_64
DEBUG util.py:444:   Problem 3: cannot install the best candidate for the job
DEBUG util.py:444:    - nothing provides python3 = 3.9.8-1.el9 needed by python3-devel-3.9.8-1.el9.x86_64
DEBUG util.py:444:    - nothing provides python3-libs(x86-64) = 3.9.8-1.el9 needed by python3-devel-3.9.8-1.el9.x86_64
Comment 1 Brian Stinson 2021-11-11 14:00:07 UTC 
We think 2 separate issues are causing trouble here. 

1.) DNF randomizes its mirror picks, and can pick different mirrors for BaseOS and AppStream during the same transaction
2.) MirrorManager validates BaseOS and AppStream as separate repositories

This means that you could pull repo metadata for a fully up-to-date, valid mirror for AppStream but get an out-of-date (but still valid) mirror for BaseOS. 

We're looking into some options here.
Comment 2 Alfredo Moralejo 2022-01-27 10:08:35 UTC 
https://bugzilla.redhat.com/show_bug.cgi?id=2046690 is a duplicate of same issue?
Comment 3 Adrian Reber 2022-01-27 14:46:35 UTC 
(In reply to Alfredo Moralejo from comment #2)
> https://bugzilla.redhat.com/show_bug.cgi?id=2046690 is a duplicate of same
> issue?

No. The outcome for the user is almost the same but this here is actually fixed.

MirrorManager includes, for up to three days, not totally up to date mirrors. We do this in Fedora to decrease the load on the primary mirrors after a new data has been pushed. We have the possibilities to disable this for really urgent security updates, but normally this is active and works for Fedora.

For CentOS Stream 9 with its three repositories, this does not work, as MirrorManager might return a not totally up to date mirror, by design, so now you can have three different mirrors and some are one or two days behind. If a package from AppStream depends on BaseOS and BaseOS is from a slightly outdated mirror you see the errors as described in this bug.

This has been fixed (worked around) by disabling the feature to offer slightly outdated mirrors too clients. This can lead to many clients using the primary mirrors for a few hours after data has been pushed. This depends on how fast mirrors are updated.

I would say this is fixed. The other bug was triggered by scanning the primary mirror while new data was pushed to the mirror and so we scanned an inconsistent state and we have no working solution for that problem.

Both problems will look the same to the user, but the underlying reason is different.
Comment 4 Josh Boyer 2022-09-28 16:01:53 UTC 
This is resolved as far as I'm aware.
Note You need to log in before you can comment on or make changes to this bug.