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.
The loop issue is fixed in bug 2113809.
As far as the LVM failure is concerned, is this reproducible all the time? The UDisks lvm2 module is known for random test failures, similar e.g. to bug 2039772 and bug 2031673.
Comment 3guazhang@redhat.com
2022-09-13 10:28:03 UTC
Yes, the failure cause by lvm module, but looks the failure info is different with bz2031673.
so I'm not sure if same one.
for the timeout error I have opened bz2039772 for RHEL8, and this bug for RHEL9.
you can close it if you think it's duplication.
the error is not always reproduced, it's random failure.
Thanks, this is on par what we're seeing in upstream CI. We'll still want to have this fixed, but the fix might not be easy. Since it's a random failure, let's treat these with low priority for the moment.