+++ This bug was initially created as a clone of Bug #1764856 +++ Description of problem: Downloaded the RHCOS QCOW2 image from access.redhat.com (verified correct SHA-256 checksum) and it won't boot on OSP. Failing at POST with "Boot failed: not a bootable disk". Version-Release number of selected component (if applicable): rhcos-4.2.0-x86_64-openstack.qcow2 SHA-256: b9225f67ae16ef38625c9669d556324d6422b29b5f6bfbd87e960062bfb37f70 How reproducible: Download above mentioned image from access.redhat.com, then upload to OSP and attempt boot from image. Steps to Reproduce: 1. Download above mentioned image from access.redhat.com 2. Upload to OSP 3. Attempt Boot from image Actual results: Fails to boot Expected results: Boot should work as with earlier versions of the RHCOS QCOW2 image. Additional info: An interesting observation is that the earlier RHCOS QCOW2 images have been much larger in size - 1.7-1.8G. This 4.2.0 image is 667MB. I suspect this image was maybe incorrectly built(?) resulting in a smaller size? --- Additional comment from Micah Abbott on 2019-10-24 13:03:32 UTC --- I think this is just a case of a missing file suffix. The OpenStack image coming out of the build pipeline is ultimately compressed via `gzip`, but during the upload process the file suffix is dropped. To confirm, I went to: https://access.redhat.com/downloads/content/290/ver=4.2/rhel---8/4.2.0/x86_64/product-software And downloaded: rhcos-4.2.0-x86_64-openstack.qcow2 Checked the sa256sum: $ sha256sum rhcos-4.2.0-x86_64-openstack.qcow2 b9225f67ae16ef38625c9669d556324d6422b29b5f6bfbd87e960062bfb37f70 rhcos-4.2.0-x86_64-openstack.qcow2 Last modified: 2019-10-16 SHA-256 Checksum: b9225f67ae16ef38625c9669d556324d6422b29b5f6bfbd87e960062bfb37f70 When I check the filetype, it shows as gzip compressed data: $ file rhcos-4.2.0-x86_64-openstack.qcow2 rhcos-4.2.0-x86_64-openstack.qcow2: gzip compressed data, was "rhcos-42.80.20191002.0-openstack.qcow2", last modified: Wed Oct 2 13:48:08 2019, from Unix, original size 1911160832 The workaround here is to rename the file with the `.gz` suffix and uncompress the file before using it. $ mv rhcos-4.2.0-x86_64-openstack.qcow2 rhcos-4.2.0-x86_64-openstack.qcow2.gz $ gunzip rhcos-4.2.0-x86_64-openstack.qcow2.gz $ file rhcos-4.2.0-x86_64-openstack.qcow2 rhcos-4.2.0-x86_64-openstack.qcow2: QEMU QCOW2 Image (v3), 17179869184 bytes I'll investigate getting the file renamed appropriately on access.redhat.com --- Additional comment from Øystein Bedin on 2019-10-24 15:59:20 UTC --- Ahh, yes, you are correct. Forgot about that piece and missed the note in the official docs. Your suggestion to rename the file would be much better to avoid this confusion. Thank you. --- Additional comment from Micah Abbott on 2019-10-24 16:16:30 UTC --- Filed card with RCM about renaming artifacts - https://projects.engineering.redhat.com/browse/RCM-69086 --- Additional comment from Micah Abbott on 2019-10-24 16:24:16 UTC --- https://jira.coreos.com/browse/GRPA-1152 --- Additional comment from Eric Paris on 2019-10-24 18:52:13 UTC --- This bug sets Target Release equal to a z-stream but has no bug in the 'Depends On' field. As such this is not a valid bug state and the target release is being unset. Any bug targeting 4.1.z must have a bug targeting 4.2 in 'Depends On.' Similarly, any bug targeting 4.2.z must have a bug with Target Release of 4.3 in 'Depends On.'
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062