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:
When displaying stopped pools, the encryption information
in the StoppedPools D-Bus property is unpacked in a manner that
unconditionally expects the structure that the value representing the
pools encryption status has if the
encryption information on the pool is consistent. This unpacking fails
with a ValueError and resulting stack trace if the encryption
information on the pool is inconsistent, as the structure of the
value being unpacked in that
case is different.
Version-Release number of selected component (if applicable):
stratis-cli-3.5.2-1.el9
How reproducible:
100%
Steps to Reproduce:
1. Create a situation where encryption information on devices in a
single stopped Stratis pool is not consistent.
2. List the stopped pools: stratis pool list --stopped
3. Observe resulting stack trace with ValueError
Actual results:
Stack trace when listing stopped pools.
Expected results:
No stack trace when listing stopped pools.
Additional info:
There are various ways to generate the inconsistent encryption
information on devices within a stopped Stratis pool. Deterministic
techniques require using cryptsetup outside of Stratis to modify the
LUKS header on a device in a Stratis pool.
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 (stratis-cli 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:6425