Public bug reported:

To address bug 2080474, we now install multipath-tools-boot when
building Ubuntu server live ISOs so that the multipath stack is present
in the initramfs.

Unfortunately, when booting the installer, the first invocation of
`multipathd -B` (as it's done by the init-top script) fails because the
/etc/multipath/bindings file does not exist:

# multipath -B -d
| multipathd v0.11.1: start up
| reconfigure: setting up paths and maps
| _check_bindings_file: fialed to read header from /etc/multipath/bindings
| ERROR: bad settings in read-only bindings file /etc/multipath/bindings
| fatal error applying configuration - aborting
| multipathd: shut down

I say _first_ invocation, because surprisingly, the failing multipathd
command still initializes the /etc/multipath/bindings file properly, so
the next invocation of the same command can succeed.

# cat /etc/multipath/bindings
# Multipath bindings, Version : 1.0
# NOTE: this file is automatically maintained by the multipath program.
# You should not need to edit this file in normal circumstances.
#
# Format:
# alias wwid
#

# multipathd -B -d
| multipathd v0.11.1: start up
| reconfigure: setting up paths and maps

The initramfs-tools hook script for multipath can copy over the
/etc/multipath/bindings file to the initramfs, but only does so if it
exists, which is not the case just after installing multipath-tools-
boot.

** Affects: multipath-tools (Ubuntu)
     Importance: Undecided
         Status: New

** Summary changed:

- multipathd fails to start in Ubuntu installer's initramfs
+ multipathd fails to start in Ubuntu installer's initramfs (no bindings file)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2120444

Title:
  multipathd fails to start in Ubuntu installer's initramfs (no bindings
  file)

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


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to