[Bug 1583563] Update Released

[Martin Pitt]

The verification of the Stable Release Update for multipath-tools has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 Released

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