Bug 2054875

Summary: multipathd.socket is missing start conditions [rhel-8.2.0.z]
Product: Red Hat Enterprise Linux 8 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED ERRATA QA Contact: Lin Li <lilin>
Severity: unspecified Docs Contact:
Priority: high    
Version: 8.5CC: abhide, agk, bmarzins, heinzm, jbrassow, lilin, mgandhi, miabbott, msnitzer, prajnoha, zkabelac
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: device-mapper-multipath-0.8.3-3.el8_2.4 Doc Type: Bug Fix
Doc Text:
Cause: The conditions for starting multipathd differed from the conditions for triggering multipathd to start from the multipathd socket. Consequence: The multipathd socket would repeatedly try starting multipathd and failing, until it eventually failed to many times, and was disabled. Fix: multipathd.socket now has the same start conditions and multipathd.service. Result: multipathd.socket will not attempt to trigger multipathd to start in cases where the start conditions in multipathd.service are not fulfilled.
 Story Points: ---
Clone Of: 2008101 Environment:
Last Closed: 2022-05-18 13:57:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2008101    
Bug Blocks:    

Comment 15 errata-xmlrpc 2022-05-18 13:57:22 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (device-mapper-multipath bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:4652