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 2005139 - major versioned latest compose symlink
Summary: major versioned latest compose symlink
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: distribution
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: RHEL Program Management
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-16 21:47 UTC by Carl George 🤠
Modified: 2024-09-15 07:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-09-15 07:29:09 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-97384 0 None None None 2021-09-16 21:49:14 UTC

Description Carl George 🤠 2021-09-16 21:47:08 UTC
Description of problem:
We currently have a latest-CentOS-Stream symlink in https://composes.stream.centos.org/production/ pointing to the latest compose.  Without an equivalent symlink including the major version (e.g. latest-CentOS-Stream-9), it's not clear what will happen when a new major version exists, or how people can reference the latest compose for each major version.


Additional info:
I'm working on code changes to fedscm_admin to support epel9-next.  Currently that tool blocks epelX and epelX-next branch requests based on packages that are in RHEL.  I'd like to have it check CentOS Stream compose metadata to block epelX-next branch requests.  I'm proceeding with that using the current latest-CentOS-Stream symlink, but in the future it needs to be switched to something that limits to a major version.

Comment 1 Troy Dawson 2022-11-02 14:29:55 UTC
This is just a quick ping to say that this is being discussed.
There are a couple of proposals for a solution and we're seeing which is best for the build environment.

Comment 2 Troy Dawson 2022-12-07 15:44:38 UTC
After much testing and probing of ODCS we have determined that we will have the following structure.

NOTE:  This is not implemented yet.  I do not have an estimate of when it will be finished.

The new structure will be

stream-{8,9,10}/{test,development,production}/latest-CentOS-Stream/

An example is currently available
https://composes.stream.centos.org/stream-9/test/latest-CentOS-Stream/

The base {test,development,production} directories will become symlinks and point to the latest stream release.
Thus production/ will point to stream-9/production for now, and when CentOS Stream 10 is released, production/ will then point to stream-10/production

Again, this is not implemented yet.  It should be before February 2023, but how much before, we currently don't know.

Comment 4 Troy Dawson 2023-02-14 14:17:45 UTC
The CentOS Stream 8 stuff is there, but it currently isn't being used in production yet.  But if you wanted to start getting scripts pointing to it you can.
https://composes.stream.centos.org/stream-8/development/
https://composes.stream.centos.org/stream-8/production/

Comment 6 Carl George 🤠 2023-03-15 20:32:22 UTC
I'd like to keep this bug open until this is completed.  After it's completed I need to submit changes to fedpkg and fedscm-admin for epel9/epel10 branch checks, and it would be nice to have this bug being closed as the reminder to go do that.

Comment 8 Troy Dawson 2023-03-15 20:47:14 UTC
Sounds good.
I expect we'll get stream-9 to be transitioned before we have to deal with stream-10.  Otherwise it will be a bit of a mess.
But I'll keep this open until we get everything in place.

Comment 10 Troy Dawson 2023-08-16 13:18:27 UTC
I've updated the stale date.
I don't think this will be completely fixed/done until CentOS Stream 10 starts getting composes built.  That won't happen for 6 months to a year.  So I've extended the stale date.

Comment 11 RHEL Program Management 2024-09-15 07:29:09 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.