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.
Descriptionguazhang@redhat.com
2022-03-24 04:21:57 UTC
Description of problem:
Found some errors in log message after start stratisd, please have a look
Version-Release number of selected component (if applicable):
stratisd-2.4.2-2.el8.x86_64
stratis-cli-2.4.2-1.el8.noarch
4.18.0-372.2.1.el8.x86_64
1. create lvm
2. cryptsetup format/open lvm
3. run some io on the luks device
4. remove luks device
5. remove lvm device
Mar 24 00:11:31 storageqe-100 systemd[1]: Started LVM event activation on device 7:0.
Mar 24 00:11:43 storageqe-100 stratisd[20514]: [2022-03-24T04:11:43Z DEBUG libstratis::engine::strat_engine::backstore::crypt::shared] Operations querying device to determine if it is a Stratis device failed with an error: Error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device.
Mar 24 00:11:45 storageqe-100 stratisd[20514]: [2022-03-24T04:11:45Z DEBUG libstratis::engine::strat_engine::backstore::crypt::shared] Operations querying device to determine if it is a Stratis device failed with an error: Error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device.
Mar 24 00:12:45 storageqe-100 kernel: XFS (dm-4): Mounting V5 Filesystem
Mar 24 00:12:45 storageqe-100 kernel: XFS (dm-4): Ending clean mount
Mar 24 00:14:35 storageqe-100 systemd[1]: tmp-libblockdev.tfq3tk1kmount_test.mount: Succeeded.
Mar 24 00:14:44 storageqe-100 kernel: XFS (dm-4): Unmounting Filesystem
Mar 24 00:14:44 storageqe-100 stratisd[20514]: Device /dev/dm-3 does not exist or access denied.
Mar 24 00:14:44 storageqe-100 stratisd[20514]: [2022-03-24T04:14:44Z WARN libstratis::engine::strat_engine::backstore::crypt::shared] Failed to acquire a context for device /dev/dm-3; failed with error: IO error occurred: Block device required (os error 15)
Mar 24 00:14:44 storageqe-100 stratisd[20514]: [2022-03-24T04:14:44Z WARN libstratis::engine::strat_engine::liminal::identify] udev identified device /dev/dm-3 as a LUKS device, but could not read LUKS header from the device, disregarding the device: Cryptsetup error: IO error occurred: Block device required (os error 15)
I'm not sure if the error message is bug or not, please confirm it.
I've tested this this message in a pre-release build of Straits 3.3 and was unable to reproduce it.
Stratis believes that the issue has been addressed. Adding this to RHEL 9.2 for QE verification.