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-01-12 12:30:23 UTC
Description of problem:
udisks2 regression testing hit the error, please have a look if hit a bug
Version-Release number of selected component (if applicable):
udisks2-2.9.4-2.el9.x86_64
libblockdev-2.25-10.el9.x86_64
https://bugzilla.redhat.com/show_bug.cgi?id=1994220 which fixed the error in libblockdev, and now hit it in udisks2.
======================================================================
ERROR: test_create (test_20_LVM.UdisksLVMVDOTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/root/rpmbuild/BUILD/udisks-2.9.4/src/tests/dbus-tests/test_20_LVM.py", line 509, in test_create
stats = lv.GetStatistics(self.no_options, dbus_interface=self.iface_prefix + '.VDOVolume')
File "/usr/lib64/python3.9/site-packages/dbus/proxies.py", line 141, in __call__
return self._connection.call_blocking(self._named_service,
File "/root/rpmbuild/BUILD/udisks-2.9.4/src/tests/dbus-tests/udiskstestcase.py", line 42, in call_long
return call(*args, **kwargs)
File "/usr/lib64/python3.9/site-packages/dbus/connection.py", line 652, in call_blocking
reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.UDisks2.Error.Failed: Error retrieving volume statistics: Error reading statistics from /sys/kvdo/udisks_test_vdo_vg-udisks_test_vdopool-vpool/statistics: Error opening directory “/sys/kvdo/udisks_test_vdo_vg-udisks_test_vdopool-vpool/statistics”: No such file or directory
This is actually a kvdo bug, see https://bugzilla.redhat.com/show_bug.cgi?id=2035003#c4 for explanation -- the sysfs API we are using to get the statistics is temporarily disabled. The error message is a little bit confusing -- we first try to use the new sysfs API, but if it fails we only log it and the try the old one and if that fails we report error, we probably should change the error message to say that we tried both.
*** This bug has been marked as a duplicate of bug 2035003 ***