[Bug 1682178] Re: multipathd.socket unit fails to start ("Failed to listen on sockets: Address already in use")

[ChristianEhrhardt]

Thank Brian for the ping here,
Of the issues found in the logs none seem all too multipath specific, seems mostly:
- ERROR: InterpreterNotFound: python3.6
- sha3-384 mismatch for "pc-kernel"
- and a bunch of file not found for various .img files

I wonder if the latter issues are due to the missing python3.6.
Overall - so far - it appears to be more issues in the ubuntu-image tests than multipath issues.
Are these known issues in ubuntu-image or is the assumption of anyone that multipath really broke something here?

-- 
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/1682178

Title:
  multipathd.socket unit fails to start ("Failed to listen on sockets:
  Address already in use")

Status in multipath-tools package in Ubuntu:
  Fix Committed
Status in multipath-tools source package in Zesty:
  Fix Committed

Bug description:
  
  [Impact]
  Multipath users on Ubuntu Server will see error messages from multipathd at boot. While the system continues to boot and is in a stable state, multipathd should be appropriately handled via its systemd unit after the system is booted.

  [Test case]
  1) Install with multipath enabled (disk-detect/multipath/enable=true).
  2) Boot the installed system
  3) Verify that there are no error messages from multipathd at boot.

  [Regression potential]
  This update changes the startup/shutdown login in initramfs at an early boot state, this could lead to failures to complete the booting process for systems that depend on multipath being available to bring up the rootfs, or failure to correctly drive multipathd/multipath-tools from a booted system. Furthermore, failures or delays shutting down a system due to multipathd / multipath-tools remaining up should also be considered as possible regressions issued from this update. 

  ---

  This bug is used to include one more patch to completely fix LP
  1670811.

  That patch is mentioned in LP 1670811 comment 15 [1].

  It addresses the case in which the initramfs instance of multipathd
  takes a while to actually shutdown after its receives the signal from
  initramfs/scripts/local-bottom/multipath.

  That shutdown is asynchronous, and keeps the multipathd socket open.
  If it is still open by the time the root fs is mounted and its units are started, the multipathd.socket will fail to start.

  Patch attached.

  Logs:
  ----

  [ 36.465332] systemd[1]: Failed to listen on multipathd control socket.
  [FAILED] Failed to listen on multipathd control socket.
  See 'systemctl status multipathd.socket' for details.

  # systemctl status multipathd.socket --no-pager -l
  * multipathd.socket - multipathd control socket
     Loaded: loaded (/lib/systemd/system/multipathd.socket; static; vendor preset: enabled)
     Active: failed (Result: resources)
     Listen: @/org/kernel/linux/storage/multipathd (Stream)

  # journalctl -b -x
  ...
  Mar 07 11:02:04 ltciofvtr-s824-lp8 systemd[1]: multipathd.socket: Failed to listen on sockets: Address already in use
  Mar 07 11:02:04 ltciofvtr-s824-lp8 systemd[1]: Failed to listen on multipathd control socket.
  Mar 07 11:02:04 ltciofvtr-s824-lp8 systemd[1]: multipathd.socket: Unit entered failed state.
  ...

  Links:
  -----

  [1] https://bugs.launchpad.net/ubuntu/+source/multipath-
  tools/+bug/1670811/comments/15

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