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.
(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?
Comment 2guazhang@redhat.com
2023-06-25 00:39:59 UTC
(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.
Comment 4guazhang@redhat.com
2023-06-27 00:28:29 UTC
yes, the testing has enabled FIPS and don't reproduce it with RHEL8.
Comment 5RHEL Program Management
2023-09-23 12:35:43 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6RHEL Program Management
2023-09-23 12:38:33 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
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]#