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.

According to https://bugzilla.redhat.com/show_bug.cgi?id=1819743#c21, report this bug.

tested with luks format, it works well.
tested with luks-inside-qcow2, hit this issue.


Versions:
kernel-4.18.0-222.el8.x86_64
qemu-kvm-4.2.0-30.module+el8.3.0+7298+c26a06b8

Maxim: can you please help clarify the status here?

This BZ is supposed to be tracking the issue in the "fast train" (RHEL-AV), but it's currently set to Product=RHEL.

And the issue is already fixed in RHEL (Bug 1819743), so I imagine it's already in QEMU-5.1 for RHEL-AV?

(In reply to Ademar Reis from comment #2)
> Maxim: can you please help clarify the status here?
> 
> This BZ is supposed to be tracking the issue in the "fast train" (RHEL-AV),
> but it's currently set to Product=RHEL.
> 
> And the issue is already fixed in RHEL (Bug 1819743), so I imagine it's
> already in QEMU-5.1 for RHEL-AV?


Just fixed luks format in Bug 1819743 and Bug 1827630.


This bug tracked the issue for luks-inside-qcow2 format.

And this bug is for slow train(RHEL), Bug 1845353 is for fast train(RHEL-AV)

Going to CLOSE this as WONTFIX for RHEL at this point.

We can revisit perhaps later once the scope of the RHEL-AV work is known and/or it's deemed a more critical problem.

Consumers of luks inside qcow2 should probably be using RHEL-AV anyway since it's closer to upstream.