Red Hat Bugzilla – Bug 592297
[RHEL6 beta1] anaconda doesn't show multipath devices
Last modified: 2010-11-10 14:43:27 EST
Description of problem:
anaconda doesn't show multipath volumes
Version-Release number of selected component:
Steps to Reproduce:
1. Start installer with "mpath" boot option
2. Choose "Specialized Storage Devices"
3. Click "Multipath Devices" tab in device selection
No devices appear in the window
Example of the actual results :
See the attached images.
While the multipath LUNs are listed up for each path (the 1st image),
they doesn't appear in the "Multipath Devices" tab (the 2nd image).
It seems the installer couldn't find their WWID (the 3rd image).
I tried choosing "Specialized Storage Devices" and/or
adding "mpath" boot option but neither did work.
Multipath devices appear in "Multipath Devices" window.
On the same test machine, the multipath devices are correctly recognized
by both installers of RHEL5 and RHEL6 Alpha3.
Attached sosreport was taken on RHEL6 Beta1 installation with
/etc/multipath.conf manually added/configured afterwards.
Created attachment 414052 [details]
screenshot of basic devices
Created attachment 414053 [details]
screenshot of multipath devices
Created attachment 414054 [details]
screenshot of device search
Created attachment 414059 [details]
multipath -v3 output from tty2 during install
Multipath has had a rough time of it lately. Before we go too far down the path of debugging this, can you please try a tree with anaconda-13.21.40-1? pjones just committed a set of multipath fixes yesterday for that build, and those have been tested with at least one multipath setup and shown to fix problems.
How to add the boot option "multipath", could you give me a detail step?
Jeff - could you attach the udevadm output I was looking for in comment #18? That'll help us determine whether this is an anaconda bug or a udev bug. Thanks.
I'm closing this bug as VERIFIED based on comment 26.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.