Bug 1508448

Summary: device-mapper-multipath package does not create configuration files properly
Product: Red Hat Enterprise Linux 7 Reporter: Michael Watters <wattersm>
Component: device-mapper-multipathAssignee: LVM and device-mapper development team <lvm-team>
Status: CLOSED DUPLICATE QA Contact: Lin Li <lilin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: agk, bmarzins, heinzm, lilin, msnitzer, prajnoha, thibaut_perrin
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-04 19:33:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Watters 2017-11-01 12:56:25 UTC
Description of problem:

After installing the device-mapper-multipath package the multipathd service will fail to start due to a missing configuration file.  systemctl status multipathd.service shows the following output.

[root@server ~]# systemctl status multipathd
● multipathd.service - Device-Mapper Multipath Device Controller
   Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Wed 2017-11-01 08:36:53 EDT; 4s ago
           ConditionPathExists=/etc/multipath.conf was not met

multipath -l also shows that the configuration file is missing.

root@server ~]# multipath -l
Nov 01 08:36:02 | DM multipath kernel driver not loaded
Nov 01 08:36:02 | /etc/multipath.conf does not exist, blacklisting all devices.
Nov 01 08:36:02 | A default multipath.conf file is located at
Nov 01 08:36:02 | /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf
Nov 01 08:36:02 | You can run /sbin/mpathconf to create or modify /etc/multipath.conf
Nov 01 08:36:02 | DM multipath kernel driver not loaded

Running /sbin/mpathconf  does not create the file as expected.  I was able to get multipathd working after manually loading the dm_multipath module and creating the configuration file by copying from another server.

Version-Release number of selected component (if applicable):

0.4.9-111

How reproducible:


Steps to Reproduce:
1. yum -y install device-mapper-multipath
2. Run multipath -l or systemctl start multipathd.service


Actual results:

multipathd.service fails to start.  /sbin/mpathconf does not generate a configuration file.

Expected results:

Configuration file is created automatically.  multipathd.service starts with no errors.

Comment 2 Thibaut Perrin 2018-01-04 10:54:28 UTC
Shouldn't you run "mpathconf --enable" instead of just mpathconf to generate the file ?

That's what the command --help states : 

usage: /usr/sbin/mpathconf <command>

Commands:
Enable: --enable
Disable: --disable


Running just mpathconf prints what should be setup in the generated multipath.conf file.

Or maybe I'm just misreading ?

Comment 3 Ben Marzinski 2018-01-04 19:33:04 UTC
oops. didn't notice this dup.

*** This bug has been marked as a duplicate of bug 1508483 ***