Bug 2214173 - Unable to verify checksum of the image in latest centos:stream8 image
Summary: Unable to verify checksum of the image in latest centos:stream8 image
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: distribution
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Troy Dawson
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-12 07:55 UTC by Delyan Yanev
Modified: 2023-06-28 08:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-27 18:07:15 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-159484 0 None None None 2023-06-12 07:59:05 UTC

Description Delyan Yanev 2023-06-12 07:55:24 UTC
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

Comment 1 Adam Samalik 2023-06-15 10:28:10 UTC
Please see my answer in https://bugzilla.redhat.com/show_bug.cgi?id=2214169 it applies here as well.

Comment 2 Delyan Yanev 2023-06-15 10:44:17 UTC
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".

Comment 3 Delyan Yanev 2023-06-20 10:13:03 UTC
@Troy Dawson Could you implement fix as you will do that in case 2214169

Comment 4 Troy Dawson 2023-06-20 17:01:37 UTC
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.

Comment 5 Troy Dawson 2023-06-27 18:07:15 UTC
I have verified that this has been fixed with this weeks compose release.

Comment 6 Delyan Yanev 2023-06-28 08:48:22 UTC
Confirmed. Thank you very much for your support.


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