Bug 2008098 - multipathd.socket is missing start conditions
Summary: multipathd.socket is missing start conditions
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: device-mapper-multipath
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: LVM and device-mapper development team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-27 09:33 UTC by Luca BRUNO
Modified: 2021-10-21 20:55 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-21 20:55:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github opensvc multipath-tools issues 15 0 None open multipathd/socket: start conditions not aligned with service unit, funky result 2021-09-27 09:33:35 UTC

Description Luca BRUNO 2021-09-27 09:33:36 UTC 
Right now the socket unit 'multipathd.socket' is missing several start conditions that are present on the service unit 'multipathd.service'.

This means that if one of the conditions is not met (e.g. kargs contains 'nompath'), a client could trigger the socket unit to start, then enter a retry loop, and eventually be marked as failed.

This kind of failure has been observed on live systems (e.g. on RHEL 8 at https://bugzilla.redhat.com/show_bug.cgi?id=1976111) and reported upstream at https://github.com/opensvc/multipath-tools/issues/15.

This ticket is a request to:
 * cherry-pick the upstream fix at https://github.com/opensvc/multipath-tools/pull/16
 * fix the custom patch at '0026-RH-don-t-start-without-a-config-file.patch' in order to mirror 'ConditionPathExists=/etc/multipath.conf' on 'multipathd.socket' too
Comment 1 Ben Marzinski 2021-10-21 20:55:54 UTC 
This fix will be in F36.
Note You need to log in before you can comment on or make changes to this bug.