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.
Description of problem:
Although there are "latest" image for CentOS 8 Stream images (e.g. https://cloud.centos.org/centos/8-stream/x86_64/images/CentOS-Stream-GenericCloud-8-latest.x86_64.qcow2) there is no checksum of the latest image into checksum file https://cloud.centos.org/centos/8-stream/x86_64/images/CHECKSUM.
Instead they contain check-sums of "timestamped" files.
For example, the https://cloud.centos.org/centos/8-stream/x86_64/images/CHECKSUM file has the following content:
# CentOS-Stream-GenericCloud-8-20230308.3.x86_64.qcow2: 1771314688 bytes
SHA256 (CentOS-Stream-GenericCloud-8-20230308.3.x86_64.qcow2) = 1ab4a628211a9178979e916f9dc59c8db67b203666aab15743ea80e17f7d4083
# CentOS-Stream-GenericCloud-8-20230501.0.x86_64.qcow2: 1665112064 bytes
SHA256 (CentOS-Stream-GenericCloud-8-20230501.0.x86_64.qcow2) = 773794fb1e54177c896d34d751ab70c8c0f30909bce963b5000d1d3915488aa7
# CentOS-Stream-GenericCloud-8-20230523.0.x86_64.qcow2: 1823070208 bytes
SHA256 (CentOS-Stream-GenericCloud-8-20230523.0.x86_64.qcow2) = b69a5198ed1d507bb350b47f6ca8f40c661e6901c25cdd93e6167a3a7474bf7e
# CentOS-Stream-GenericCloud-8-20230530.1.x86_64.qcow2: 1831375872 bytes
SHA256 (CentOS-Stream-GenericCloud-8-20230530.1.x86_64.qcow2) = 8e9e8cb13a79f49d6a0378b001411d1558875ec5594e01427feb6811f86f9fbd
# CentOS-Stream-GenericCloud-8-20230606.0.x86_64.qcow2: 1804198912 bytes
SHA256 (CentOS-Stream-GenericCloud-8-20230606.0.x86_64.qcow2) = b8bf004b0f1d9924d9516ff4ad1ecfcf2300469d811a18bc605c45c9732faaaa
# CentOS-Stream-GenericCloud-8-20230606.0.x86_64.qcow2: 1804198912 bytes
SHA256 (CentOS-Stream-GenericCloud-8-20230606.0.x86_64.qcow2) = b8bf004b0f1d9924d9516ff4ad1ecfcf2300469d811a18bc605c45c9732faaaa
so it can't be used to verify the latest CentOS-Stream-GenericCloud-8-latest.x86_64.qcow2 file.
Version-Release number of selected component (if applicable):
CentOS Stream 8
How reproducible:
Steps to Reproduce:
1. Download the https://cloud.centos.org/centos/8-stream/x86_64/images/CentOS-Stream-GenericCloud-8-latest.x86_64.qcow2 file
2. Download the https://cloud.centos.org/centos/8-stream/x86_64/images/CHECKSUM file
3. Run the following command:
sha256sum -c CHECKSUM
Actual results:
It fails with the following output:
Expected results:
It should pass the check:
CentOS-Stream-GenericCloud-8-latest.x86_64.qcow2: OK
Additional info:
We cannot verify the content and use the latest image
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".
Yes.
The same fix that fixes this for centos stream 9 also fixes it for centos stream 8.
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.