Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
For backwards compatibility, osbuild-composer wants to explicitly select qcow2 v2, rather than the default v3 when building qcow2 images for RHEL8.4. This is what was done in RHEL8.3 (before osbuild-composer was used) and ensures compatibility with RHEL6 hosts.
Extend the osbuild manifest format to allow explicit selection of the qcow2 version.
I see:
$ qemu-img info rhel-guest-image-8.4-754.x86_64.qcow2
image: rhel-guest-image-8.4-754.x86_64.qcow2
file format: qcow2
virtual size: 10 GiB (10737418240 bytes)
disk size: 684 MiB
cluster_size: 65536
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
I expect:
$ qemu-img info rhel-guest-image-8.4-754.x86_64.qcow2
image: rhel-guest-image-8.4-754.x86_64.qcow2
file format: qcow2
virtual size: 10 GiB (10737418240 bytes)
disk size: 1.24 GiB
cluster_size: 65536
Format specific information:
compat: 0.10
compression type: zlib
refcount bits: 16
Comment 3Christian Kellner
2021-04-07 16:24:56 UTC
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 (osbuild bug fix and enhancement update), 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-2021:1825
For backwards compatibility, osbuild-composer wants to explicitly select qcow2 v2, rather than the default v3 when building qcow2 images for RHEL8.4. This is what was done in RHEL8.3 (before osbuild-composer was used) and ensures compatibility with RHEL6 hosts. Extend the osbuild manifest format to allow explicit selection of the qcow2 version. I see: $ qemu-img info rhel-guest-image-8.4-754.x86_64.qcow2 image: rhel-guest-image-8.4-754.x86_64.qcow2 file format: qcow2 virtual size: 10 GiB (10737418240 bytes) disk size: 684 MiB cluster_size: 65536 Format specific information: compat: 1.1 compression type: zlib lazy refcounts: false refcount bits: 16 corrupt: false I expect: $ qemu-img info rhel-guest-image-8.4-754.x86_64.qcow2 image: rhel-guest-image-8.4-754.x86_64.qcow2 file format: qcow2 virtual size: 10 GiB (10737418240 bytes) disk size: 1.24 GiB cluster_size: 65536 Format specific information: compat: 0.10 compression type: zlib refcount bits: 16