On Thu, Mar 30, 2017 at 6:29 PM, Mauricio Faria de Oliveira < [email protected]> wrote:
> BTW, the other/duplicate bug of this, is on 16.04. > Can you please upload your fix for it too? > 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. 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. [1]: https://launchpadlibrarian.net/313425549/buildlog_ubuntu-zesty-ppc64el.multipath-tools_0.6.4-3ubuntu3_BUILDING.txt.gz -- 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
