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.
Thanks for reporting this!
The latest image is technically just a symlink to the "dated" image. So right now these two should be the same:
CentOS-Stream-GenericCloud-9-latest.x86_64.qcow2
CentOS-Stream-GenericCloud-9-20230612.0.x86_64.qcow2
But the -latest one isn't listed, you're right.
As a workaround, can you please use the "dated" image? (Or check the checksum of the -latest against the dated entry?)
I opened https://issues.redhat.com/browse/CS-1643 to track the work.
This workaround is not very useful in the CI/CD cycle because we need to use the "latest" static image name and if the content of the checksum and name of the image is not part of the checksum files the verification will failed with "No such file or directory".
You are correct.
When I setup the -latest things, my mind totally blanked on how checksums are used.
I've already got a fix in our scripts.
Next weeks push out of the weekly compose should have things correct.
I can fix CentOS Stream 8's (2214173) but not CentOS Linux 7 (2214178). I have no access to the 7 infrastructure.
Note: We had some compose failures on this weeks CentOS Stream 8 and 9 production composes, so this weeks releases are taking longer than usual.