Bug 2214169
| Summary: | Unable to verify checksum of the image in latest centos:stream9 image | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Delyan Yanev <delyan.yanev> |
| Component: | distribution | Assignee: | Troy Dawson <tdawson> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Release Test Team <release-test-team> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | CentOS Stream | CC: | bstinson, jwboyer, tdawson |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-06-27 18:06:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Delyan Yanev
2023-06-12 07:44:09 UTC
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. Thank you for your support and help. Could you adapt also the other cases 2214173 and 2214178. Thanks in advance. 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. I have verified that this has been fixed with this weeks compose release. Confirmed. Thank you very much for your support. |