https://bugzilla.suse.com/show_bug.cgi?id=1202041 Bug ID: 1202041 Summary: Images and sha256 out of sync on mirrors Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Images Assignee: public-cloud-maintainers@suse.de Reporter: iwienand@redhat.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- We have some suse based CI jobs that periodically fail when checking the sha256 hash after downloading qcow2 images for testing. One example is from 2022-07-11 at https://paste.opendev.org/show/b1r9oMWXQNHzqmsTGcx9/ Today (2022-08-01) we are seeing similar issues clarkb> the data I have is earlier today I downlodaed the file and got sha256sum b77c0c48f970c00ab9c99a574114f41d54c12a51c4d29e31e2945bfdf28dc9c8 for the actual file but the sha256sum file on the webserver says 864667deb442174c05d5fb8cd2dd9a8165ded0fb13f31ea7e96139ab911a7531 I managed to replicate this https://paste.opendev.org/show/bJmBLrJrJQtXoQjx37hT/ what is seems to me is that "provo-mirror" is out of sync; but it's sha256 file is consistent with the .qcow2 it serves. However on another mirror (the one I seem to get sent to ends up at mirror.firstyear.id.au) we see a different, but mirror-consistent hash. I'm not sure which mirror is correct, but it seems to me that what must be happening for some users and our CI occasionally is that we get the .qcow2 from one location, and then the .sha256 file from another, and they don't match. This might be more common for users in the US where I presume there is a higher round-robbin of similar mirrors, rather than for me out in Australia where I probably always get sent to the same mirror. -- You are receiving this mail because: You are on the CC list for the bug.