Description of problem: Although there are "latest" image for CentOS 7 images (e.g. https://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2) there is no checksum of the latest image into checksum file https://cloud.centos.org/centos/7/images/sha256sum.txt. Instead they contain check-sums of "version" files. For example, the https://cloud.centos.org/centos/7/images/sha256sum.txt file has the following content: 1db30c9c272fb37b00111b93dcebff16c278384755bdbe158559e9c240b73b80 CentOS-7-x86_64-GenericCloud-2003.qcow2 b7555ecf90b24111f2efbc03c1e80f7b38f1e1fc7e1b15d8fee277d1a4575e87 CentOS-7-x86_64-GenericCloud-2003.qcow2c 963866edac9150db8b5c04df9ae80273a11eec6218f114cbb96cb4b53e33803c CentOS-7-x86_64-GenericCloud-2003.qcow2.xz 100e0fd9ffde6259fa9156090bf11258124a6ade8c91ea6f43cb47cca07f7b0e CentOS-7-x86_64-GenericCloud-2003.raw.tar.gz 51c0222aa4bc7d966fc044eb6ce9182993a1dc398eaa595e58abd0d361439baf CentOS-7-aarch64-GenericCloud-2009.qcow2 f08fde34542218e8750a8655001a31489b0e9fe7ecd15aca28cb121e4e9d7121 CentOS-7-aarch64-GenericCloud-2009.qcow2c 4e8c53386406efea88c3c5d2b0b6df123a3a4cd37dc868921c706a003cc2ae34 CentOS-7-ppc64le-GenericCloud-2009.qcow2 ec97bb60d0c962a78730ea55f4dbb930a1e3d4a9eb880c4177d0ebd99aa70c18 CentOS-7-ppc64le-GenericCloud-2009.qcow2c e38bab0475cc6d004d2e17015969c659e5a308111851b0e2715e84646035bdd3 CentOS-7-x86_64-GenericCloud-2009.qcow2 7ba4513d96591496213a07bbe25e3eb643d61491924c8548a91815b420fd9827 CentOS-7-x86_64-GenericCloud-2009.qcow2c so it can't be used to verify the latest CentOS-7-x86_64-GenericCloud.qcow2 file. Version-Release number of selected component (if applicable): CentOS 7 How reproducible: Steps to Reproduce: 1. Download the https://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 file 2. Download the https://cloud.centos.org/centos/7/images/sha256sum.txt 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-7-x86_64-GenericCloud.qcow2: OK Additional info: We cannot verify the content and use the latest image
Please see my answer in https://bugzilla.redhat.com/show_bug.cgi?id=2214169 it applies here as well.
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".
@Troy Dawson Could you implement fix as you will do that in case 2214169
I have no access to the CentOS Linux 7 release process and infrastructure. So no. I'm not saying this won't get fixed. But it won't be by me.
Could you route the ticket to the right team and person. Thank you in advance.
Latest is just a symlink to the last created package. I can certainly add that to the file // I doubt we will generate any other CentOS-7 images there anyway. I'll update momentarily.
The un-versioned sha256sums have been added to the master server, this should now work, once the stand rsyncs to mirrors happen (approximately 30 mins from now). Lets us know if everything is working as planned now.
Everything works as expected. You can close the case. Thanks you very much for your support.