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.

(filed against distribution because the component is not in Bugzilla)

centos-stream-release-9.0-1.0.4.el9.noarch is in the buildroot, but cannot be rebuilt. No SRPM can be created because the Git repository is missing. checkout.log from the buildSRPMFromSCM task contains:

$ git clone -n https://gitlab.com/redhat/centos-stream/rpms/centos-stream-release /var/lib/mock/c9s-build-67393-16836/root/chroot_tmpdir/scmroot/centos-stream-release
Cloning into '/var/lib/mock/c9s-build-67393-16836/root/chroot_tmpdir/scmroot/centos-stream-release'...
fatal: could not read Username for 'https://gitlab.com': No such device or address

But the repository does not exist, not even after Gitlab SSO login.

https://gitlab.com/redhat/centos-stream/rpms/centos-release

(In reply to Josh Boyer from comment #1)
> https://gitlab.com/redhat/centos-stream/rpms/centos-release

Uh-oh. Is there a reason why the repository and the SRPM name do not match? It makes the repository quite difficult to discover.

Is such a discrepancy common? Thanks.

It's not common as far as I know, outside of the issues that gitlab has with "tree" and packages with a + in their name (which should be covered by syncing).  There is/was a similar case with dump/restore but that is the only other package I can think of off the top of my head that has a mismatch that isn't forced by gitlab limitations.

My guess is that it doesn't match because centos-release existed before Stream existed, and they retrofitted the existing repo because it's already there for CS8.  Brian could comment further.