[Bug 1578638] Re: multipath tools wrong dependecy

[Brian Murray]

Hello sles, 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: Triaged => 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/1578638

Title:
  multipath tools wrong dependecy

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.

  
  16.04:

  /etc/init.d/multipath-tools

  # Required-Start:    udev $local_fs $remote_fs $syslog

  $remote_fs s wrong here, because it results in:

  root at inetgw2:/etc/init.d# journalctl -x | grep mpath
  май 05 16:53:46 inetgw2 ocfs2[1459]: Starting Oracle Cluster File System (OCFS2) mount.ocfs2: Device name specified was not found while opening device /dev/mapper/mpatha
  май 05 16:55:15 inetgw2 systemd[1]: dev-mapper-mpatha.device: Job dev-mapper-mpatha.device/start timed out.
  май 05 16:55:15 inetgw2 systemd[1]: Timed out waiting for device dev-mapper-mpatha.device.
  -- Subject: Ошибка юнита dev-mapper-mpatha.device
  -- Произошел сбой юнита dev-mapper-mpatha.device.
  май 05 16:55:15 inetgw2 systemd[1]: dev-mapper-mpatha.device: Job dev-mapper-mpatha.device/start failed with result 'timeout'.
  май 05 16:55:16 inetgw2 multipathd[1690]: mpatha: load table [0 314572800 multipath 1 queue_if_no_path 0 2 1 round-robin 0 2 1 8:32 1000 8:48 1000 round-robin 0 2 1 8:16 1000 8:64 1000]

  i.e. multipathd is started _after_ systemd tries mount.

  looks like removing  $remote_fs solves problem.

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1578638/+subscriptions