[Bug 1583563] Re: System will not start with multipathd enabled
Brian Murray
brian at ubuntu.com
Thu Jun 23 21:08:51 UTC 2016
Hello mike99mac, or anyone else affected,
Accepted multipath-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/multipath-
tools/0.5.0+git1.656f8865-5ubuntu2.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: multipath-tools (Ubuntu Xenial)
Status: Confirmed => Fix Committed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1583563
Title:
System will not start with multipathd enabled
Status in multipath-tools package in Ubuntu:
Fix Released
Status in multipath-tools source package in Xenial:
Fix Committed
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.service" unit.
* 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1583563/+subscriptions
More information about the foundations-bugs
mailing list