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.
This bug was initially created as a copy of Bug #2030647
I am copying this bug because: we now see the same issue on RHEL 8.7 too.
Test test case randomly fails for both LVM DBus and LVM CLI. The test fails when we try to remove a newly created striped LV, I assume the tests in gating run on a slow machine and the LV is not fully synced when we try to remove it. We don't see this type of failure in our CI.
======================================================================
ERROR: test_lvcreate_type (lvm_dbus_tests.LvmTestLVcreateType)
Verify it's possible to create LVs with various types
----------------------------------------------------------------------
Traceback (most recent call last):
File "/var/str/source/tests/lvm_dbus_tests.py", line 812, in test_lvcreate_type
succ = BlockDev.lvm_lvremove("testVG", "testLV", True, None)
File "/usr/lib64/python3.9/site-packages/gi/overrides/BlockDev.py", line 590, in lvm_lvremove
return _lvm_lvremove(vg_name, lv_name, force, extra)
gi.repository.GLib.GError: g-bd-lvm-error-quark: Running 'Remove' method on the '/com/redhat/lvmdbus1/Lv/30' object failed: ('com.redhat.lvmdbus1.Lv', 'Exit code 5, stderr = Logical volume testVG/testLV in use.\n') (7)
======================================================================
ERROR: test_lvcreate_type (lvm_test.LvmTestLVcreateType)
Verify it's possible to create LVs with various types
----------------------------------------------------------------------
Traceback (most recent call last):
File "/var/str/source/tests/lvm_test.py", line 748, in test_lvcreate_type
succ = BlockDev.lvm_lvremove("testVG", "testLV", True, None)
File "/usr/lib64/python3.9/site-packages/gi/overrides/BlockDev.py", line 590, in lvm_lvremove
return _lvm_lvremove(vg_name, lv_name, force, extra)
gi.repository.GLib.GError: g-bd-utils-exec-error-quark: Process reported exit code 5: Logical volume testVG/testLV in use.
(0)
The fix for this issue is included in the upstream release 2.28 we rebased to in 8.8 so I am closing this as a duplicate of the rebase bug.
*** This bug has been marked as a duplicate of bug 2123347 ***