System will not start with multipathd enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
multipath-tools (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Xenial |
Fix Released
|
High
|
Dimitri John Ledkov |
Bug Description
[Impact]
* Both systemd units and init scripts are shipped for multipath-tools.
* However units did not correctly take priority, as initscripts and units names did not match.
* Further more multipath-tools was miscompiled without systemd support for Type=Notify unit
[Test Case]
* Using service command, init script, or systemctl commands starting "multipath-tools" should operate on systemd "multipathd.
* Systems must boot with multipath-tools installed correctly, and multipathd.service started.
If I do these three commands on a fresh Ubuntu clone which has one pair of FCP devices pointing to a LUN:
# apt-get -y install multipath-tools
# systemctl enable multipathd
# reboot
The system will not come back up. It seems to spin with the messages: “A start job is running for Device-M...vice Controller (<x> / 1min 30s)” In 90 seconds it times out and starts counting again.
Changed in ubuntu-z-systems: | |
status: | New → Triaged |
tags: | added: s390x |
Changed in ubuntu-z-systems: | |
assignee: | nobody → Canonical Server Team (canonical-server) |
Changed in multipath-tools (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in multipath-tools (Ubuntu): | |
status: | In Progress → Confirmed |
description: | updated |
Changed in multipath-tools (Ubuntu Xenial): | |
assignee: | nobody → Louis Bouchard (louis-bouchard) |
Changed in multipath-tools (Ubuntu Xenial): | |
assignee: | Louis Bouchard (louis-bouchard) → Dimitri John Ledkov (xnox) |
tags: |
added: verification-done removed: verification-needed |
That's expected. one must configure multipath devices too, if enabling this post-install.
Or use installer to install system onto multipath devices from the start, with correct multipath config, fstab and zipl.