Christian,
> I assume you mean you full fix to go back to 16.04/16.10.
> But please bear in mind that the fix uploaded for now is only doing the
> "use /run instead of /var/run" change.
> I might miss something here, but IMHO that is only valid in zesty.
Or maybe me. I'll go check in 16.04.x, because there was a bug report
here with 16.04.x in which I indeed saw multipathd not being killed
on initramfs's local-bottom script.
And it seems even weirder that I just checked that system's initramfs
and it has both /var/run and /run as normal directories (so not sure
that kill has failed at all).
# lsb_release -d
Description: Ubuntu 16.04.2 LTS
# gzip -dc /boot/initrd.img-$(uname -r) | cpio -id
# ls -ld run var/run
drwxr-xr-x 2 root root 40 Apr 6 05:40 run
drwxr-xr-x 2 root root 40 Apr 6 05:40 var/run
I'll go check that out.
> Zesty has -DRUN_DIR=\"run\" see [1] and in the code using it:
> libmultipath/defaults.h:45:#define DEFAULT_PIDFILE "/" RUN_DIR
> "/multipathd.pid"
> But former Xenial/Yakkety versions have:
> libmultipath/defaults.h:29:#define DEFAULT_PIDFILE
> "/var/run/multipathd.pid"
> So for X/Y we will need to sort out the renewal of the bottom code as
> Cyphermox mentioned, and once we know how it looks like consider SRU'ing
> that back.
Okay. I'll go check the 16.04.x problem and follow up here.
cheers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670811
Title:
Multipath services fails to start on Ubuntu 17.04 on boot and kdump
(initramfs)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1670811/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
