** Description changed: - If I do these three commands on a fresh Ubuntu clone which has one pair - of FCP devices pointing to a LUN: + [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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583563 Title: System will not start with multipathd enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1583563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
