Description of problem: udisks2 regression job failed because of the error, please have a look Version-Release number of selected component (if applicable): udisks2-2.9.0-15.el8.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: [root@amd-genoa-04 udisks-2.9.0]# python3 src/tests/dbus-tests/run_tests.py -s test_19_lsm.UdisksLSMTestCase Configuration restored from src/tests/dbus-tests/targetcli_config.json Not spawning own process: testing the system installed instance. test_drive_lsm (test_19_lsm.UdisksLSMTestCase) ... FAIL test_drive_lsm_local (test_19_lsm.UdisksLSMTestCase) ... FAIL ====================================================================== FAIL: test_drive_lsm (test_19_lsm.UdisksLSMTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/root/rpmbuild/BUILD/udisks-2.9.0/src/tests/dbus-tests/test_19_lsm.py", line 102, in setUp self.fail('Call to lsmcli failed: %s' % out) AssertionError: Call to lsmcli failed: TRANSPORT_COMMUNICATION(400): Error while reading a message from the plug-in Data: [Errno 104] Connection reset by peer ====================================================================== FAIL: test_drive_lsm_local (test_19_lsm.UdisksLSMTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/root/rpmbuild/BUILD/udisks-2.9.0/src/tests/dbus-tests/test_19_lsm.py", line 125, in setUp self.fail('Previous libstoragemgmt database initialization error, skipping') AssertionError: Previous libstoragemgmt database initialization error, skipping ---------------------------------------------------------------------- Ran 2 tests in 0.460s FAILED (failures=2) All configuration cleared [root@amd-genoa-04 udisks-2.9.0]# uname -a Linux amd-genoa-04.khw1.lab.eng.bos.redhat.com 4.18.0-494.el8.x86_64 #1 SMP Mon May 22 11:16:32 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux [root@amd-genoa-04 udisks-2.9.0]#
(In reply to guazhang from comment #0) > TRANSPORT_COMMUNICATION(400): Error while reading a message from the plug-in > Data: [Errno 104] Connection reset by peer This looks like a libstoragemgmt issue. Looks like a crash - is there anything in the logs? Any coredumps?
Hi, Maybe it blocked by https://issues.redhat.com/browse/RHEL-376
(In reply to guazhang from comment #2) > Maybe it blocked by https://issues.redhat.com/browse/RHEL-376 Perhaps, was your test attempt made with FIPS enabled? The ticket mentions fixed libstoragemgmt-1.9.7-2.el9 build, that's RHEL9 only however.
yes, the testing has enabled FIPS and don't reproduce it with RHEL8.