[Bug 1004243] Re: multipath installs not working
Mathew Hodson
mathew.hodson at gmail.com
Mon Oct 27 05:51:54 UTC 2014
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1004243
Title:
multipath installs not working
Status in “multipath-tools” package in Ubuntu:
Fix Released
Status in “multipath-tools” source package in Precise:
Fix Released
Status in “multipath-tools” source package in Trusty:
Fix Released
Bug description:
[SRU Justification]
multipath no workie, see the original description
[Regression Potential]
In theory, multipath suddenly working again could be surprising to people who have worked around it being broken for so long. This seems unlikely.
[Test case]
Boot a d-i install with disk-detect/multipath/enable=true, and once the udebs
have been installed, drop to a shell and try to run 'multipath' to see if it explodes with a symbol resolution error. Ideally it won't.
[Original report]
I started up a precise/netboot install using debian-installer_20101020ubuntu136 and disk-detect/multipath/enable=true and found that multipath support didn't appear to be working. That is to say, both paths appeared as separate disks in the installer, and no device-mapper devices were instantiated.
I dropped to a shell and discovered that /sbin/multipath fails to run:
BusyBox v1.18.5 (Ubuntu 1:1.18.5-1ubuntu4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
~ # multipath
multipath: symbol lookup error: /lib/libmultipath.so.0: undefined symbol: dlopen
Note: this also seems to be the case in oneiric, though oneiric also
has a bug where it does not appear to have the dm-multipath module
available at install time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1004243/+subscriptions
More information about the foundations-bugs
mailing list