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.
Description of problem:
It is possible for stratisd to overwrite LUKS2 metadata, rendering the
device's data inaccessible.
Version-Release number of selected component (if applicable):
stratisd-3.5.7-1.el9
How reproducible:
The bug occurs consistently but under specific conditions which are
very hard to reproduce. What needs to happen is that stratisd fails to
unlock all devices when starting an encrypted pool and then fails to
teardown all the encrypted devices when rolling back the unlock
actions, leaving at least one device in an unlocked state. At this
point the pool is not fully set up. But, if the pool is then setup and
if stratisd writes Stratis pool level metadata to the pool devices, it
will overwrite the LUKS metadata on one of the devices in the pool,
rendering that device unopenable once it has been closed.
Steps to Reproduce:
Not specified. Chaotically starting and stopping a pool while
simultaneously but intermittently reading data from the opened crypt
devices in the pool might work.
Actual results:
Pool can not be started because pool data device can not be unlocked
because LUKS2 metadata has been overwritten.
Expected results:
It should always be possible to start an encrypted pool, so long as an
appropriate unlock mechanism is in place.
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 (stratisd 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-2023:6424