Bug 703566

Summary: All 5.7 installs to systems that had RHEL 6 installed and have SAN disks that were in a VG fail.
Product: Red Hat Enterprise Linux 5 Reporter: Barry Donahue <bdonahue>
Component: anacondaAssignee: Ales Kozumplik <akozumpl>
Status: CLOSED NOTABUG QA Contact: Release Test Team <release-test-team>
Severity: urgent Docs Contact:
Priority: high    
Version: 5.7CC: akozumpl, jzeleny, nstraz, ohudlick
Target Milestone: betaKeywords: TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-12 15:54:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
anaconda log
none
console log
none
kick start file
none
lvm log
none
sys log none

Description Barry Donahue 2011-05-10 17:21:51 UTC
Created attachment 498108 [details]
anaconda log

Description of problem: I have some systems that have SAN data disks attached. When they were installed with 6.1 the SAN disks were part of the VG that contained the boot disk etc. Now that I am trying to install 5.7 on those systems, the install fails when it tries to create the VG/LV for the install. This seems to happen on every system that had RHEL 6.1 installed and did an LVM install.

logs will be attached.

Comment 1 Barry Donahue 2011-05-10 17:22:22 UTC
Created attachment 498109 [details]
console log

Comment 2 Barry Donahue 2011-05-10 17:22:47 UTC
Created attachment 498110 [details]
kick start file

Comment 3 Barry Donahue 2011-05-10 17:23:09 UTC
Created attachment 498112 [details]
lvm log

Comment 4 Barry Donahue 2011-05-10 17:23:25 UTC
Created attachment 498113 [details]
sys log

Comment 5 Ales Kozumplik 2011-05-11 08:07:43 UTC
Barry can you lend me one of the machines where you see this in beaker? If you restart the rhel5 installation, does it succeed the second time?

Also, do you mean multipath by SAN? Because if multipath was used in RHEL6 for the PV then RHEL5 might be confused when it sees five devices with the same UUID. If you think that might be the case, try with 'multipath' on the kernel command line before starting the rhel5 installation.

Comment 6 Barry Donahue 2011-05-11 13:43:20 UTC
I just loaned you storageqe-07.lab.bos.redhat.com

Comment 9 Ales Kozumplik 2011-05-12 15:54:27 UTC
Barry,

I tried the default beaker install of 0510 rhel5 nightly on the machine and it indeed fails. However I found that the drives /dev/sde through /dev/sdk are the same multipath device. In those cases the rhel5 installer needs to be told to switch to 'multipath mode', by the mpath boot parameter:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Installation_Guide/ch-bootopts-x86.html

I think if this particular machine keeps the multipath device connected the 'mpath' command line boot option should be added to the default options in beaker.

I think we can close this as not a bug.

Comment 10 Barry Donahue 2011-05-12 17:15:47 UTC
I thought I had tried that but clearly not. thanks,

Comment 11 Ales Kozumplik 2011-05-13 06:20:44 UTC
(In reply to comment #10)
> I thought I had tried that but clearly not. thanks,

maybe because I misinformed you in comment 5. the kernel option is "mpath" not "multipath".