Good day,
I initially posted this issue on CentOS-mirror a week ago but did not receive any response.
I'm looking for a resolution to a small issue with the cloud image repository for the latest CentOS-7 image.
As far as I understand, the latest release of the CentOS-7 image should always be posted to http://cloud.centos.org/centos/7/images/CentOS-7-x86_ 64-GenericCloud.qcow2
The checksum of this file should match the highest numbered version of the cloud image listed in http://cloud.centos.org/centos/7/images/sha256sum.txt
However, the actual checksum for CentOS-7-x86_64-GenericCloud.qcow2 is returning as b56ed1a3a489733d3ff91aca2011f8720c0540b9aa27e46dd0b4f575318dd1fa which matches for CentOS-7-x86_64-GenericCloud-1608.qcow2 but NOT CentOS-7-x86_64-GenericCloud-1612.qcow2.
The latest image available should be CentOS-7-x86_64-GenericCloud-1612.qcow2 with a checksum of 559bebb4abb2fdf3bd88c917cc11ef b1975bfe4494e666d133a3148ec4e6225d.
To further the confusion, the 'Last modified' image is CentOS-7-x86_64-GenericCloud-1611.qcow2 and not -1612.
I picked up on this discrepancy because I have a script that monitors & updates our openstack images when new images become available for various distributions.
If someone could please correct these inconsistencies it would be greatly appreciated.
Thanks,
Jared Baker
On 09/02/17 19:20, Jared Baker wrote:
Good day,
I initially posted this issue on CentOS-mirror a week ago but did not receive any response.
I'm looking for a resolution to a small issue with the cloud image repository for the latest CentOS-7 image.
As far as I understand, the latest release of the CentOS-7 image should always be posted to http://cloud.centos.org/centos/7/images/CentOS-7-x86_ 64-GenericCloud.qcow2
The checksum of this file should match the highest numbered version of the cloud image listed in http://cloud.centos.org/centos/7/images/sha256sum.txt
However, the actual checksum for CentOS-7-x86_64-GenericCloud.qcow2 is returning as b56ed1a3a489733d3ff91aca2011f8720c0540b9aa27e46dd0b4f575318dd1fa which matches for CentOS-7-x86_64-GenericCloud-1608.qcow2 but NOT CentOS-7-x86_64-GenericCloud-1612.qcow2.
The latest image available should be CentOS-7-x86_64-GenericCloud-1612.qcow2 with a checksum of 559bebb4abb2fdf3bd88c917cc11ef b1975bfe4494e666d133a3148ec4e6225d.
To further the confusion, the 'Last modified' image is CentOS-7-x86_64-GenericCloud-1611.qcow2 and not -1612.
I picked up on this discrepancy because I have a script that monitors & updates our openstack images when new images become available for various distributions.
If someone could please correct these inconsistencies it would be greatly appreciated.
Thanks,
Jared Baker _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
let me see if we can get this fixed and cleared out a bit
On 02/09/2017 01:20 PM, Jared Baker wrote:
Good day,
I initially posted this issue on CentOS-mirror a week ago but did not receive any response.
I'm looking for a resolution to a small issue with the cloud image repository for the latest CentOS-7 image.
As far as I understand, the latest release of the CentOS-7 image should always be posted to http://cloud.centos.org/centos/7/images/CentOS-7-x86_ 64-GenericCloud.qcow2
The checksum of this file should match the highest numbered version of the cloud image listed in http://cloud.centos.org/centos/7/images/sha256sum.txt
However, the actual checksum for CentOS-7-x86_64-GenericCloud.qcow2 is returning as b56ed1a3a489733d3ff91aca2011f8720c0540b9aa27e46dd0b4f575318dd1fa which matches for CentOS-7-x86_64-GenericCloud-1608.qcow2 but NOT CentOS-7-x86_64-GenericCloud-1612.qcow2.
The latest image available should be CentOS-7-x86_64-GenericCloud-1612.qcow2 with a checksum of 559bebb4abb2fdf3bd88c917cc11ef b1975bfe4494e666d133a3148ec4e6225d.
To further the confusion, the 'Last modified' image is CentOS-7-x86_64-GenericCloud-1611.qcow2 and not -1612.
I picked up on this discrepancy because I have a script that monitors & updates our openstack images when new images become available for various distributions.
If someone could please correct these inconsistencies it would be greatly appreciated.
All of the latest images are pointing at *1701* now.
I also tested the images against the shasums and they passed:
[centos@master-1 images]$ sha256sum -c test.txt CentOS-7-x86_64-GenericCloud-1611.qcow2: OK CentOS-7-x86_64-GenericCloud-1611.qcow2c: OK CentOS-7-x86_64-GenericCloud-1611.qcow2.xz: OK CentOS-7-x86_64-GenericCloud-1611.raw.tar.gz: OK CentOS-7-x86_64-GenericCloud-1612.qcow2: OK CentOS-7-x86_64-GenericCloud-1612.qcow2c: OK CentOS-7-x86_64-GenericCloud-1612.qcow2.xz: OK CentOS-7-x86_64-GenericCloud-1612.raw.tar.gz: OK
The dates are not important .. it just so happened that the 1612 files were created before the 1611 ones and the 1611 ones were added later .. because 1611 is OS release, we put them up as well.
There may also be a period when testing happens, so the LATEST AVAILABLE is really the LATEST AVAILABLE that is tested. At the time, 1608 was the latest verified image.
But regardless, since 10 Feb, the 1701 images are latest and latest verified.