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.
DescriptionMichael 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.
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 ?
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.