Description of problem: I'm trying to do an install to SAN disks. The install works fine if there are 4 or less disks configured but fails if there is a fifth disk
Version-Release number of selected component (if applicable):
anaconda version 13.21.56
Running anaconda 13.21.56, the Red Hat Enterprise Linux system installer - please wait.
Examining storage devices
Creating device /dev/mapper/mpathap1
Creating ext4 filesystem on /dev/mapper/mpathap1
Creating device /dev/mapper/mpathap2
Creating physical volume (LVM) on /dev/mapper/mpathap2
Creating device /dev/mapper/mpathbp1
Creating physical volume (LVM) on /dev/mapper/mpathbp1
Creating device /dev/mapper/mpathcp1
Creating physical volume (LVM) on /dev/mapper/mpathcp1
Creating device /dev/mapper/mpathdp1
Creating physical volume (LVM) on /dev/mapper/mpathdp1
Creating device /dev/mapper/mpathep1
Creating physical volume (LVM) on /dev/mapper/mpathep1
Command line mode requires all choices to be specified in a kickstart configuration file.
Storage Activation Failed
An error was encountered while activating your storage configuration.
pvcreate failed for /dev/mapper/mpathep1: 15:57:42,423 ERROR : Device /dev/mapper/mpathep1 not found (or ignored by filtering).
('custom', ['_File Bug', '_Exit installer'])
Created attachment 432855 [details]
Created attachment 432856 [details]
Created attachment 432857 [details]
Created attachment 432858 [details]
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Does /dev/mapper/mpathep1 even exist?
Yes it does. I've experimented with this and discovered that if I have 4 SAN disks the install will succeed but the fifth will make it fail. mpathe is the 5th disk.
Where are we on this one? Is it still happening as of snapshot 8?
I'll try snap 8 tomorrow, 7/23.
I Hit the bug on what will be snap-8 RHEL6.0-20100722.0.
Can you attach /tmp/program.log as well?
Created attachment 434752 [details]
here it is.
can you please test with the latest storage code and upload a fresh traceback
in case you encounter an exception?
I tried this with RHEL6.0-20100730.5 and got the following traceback.
Looking for installation images on CD device /dev/sr0Running anaconda 13.21.66, the Red Hat Enterprise Linux system installer - please wait.
Examining storage devices
anaconda 13.21.66 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/storage/devicetree.py", line 2029, in populate
mp_info = udev_get_block_device(mp.sysfs_path)
File "/usr/lib/anaconda/storage/__init__.py", line 385, in reset
File "/usr/lib/anaconda/storage/__init__.py", line 103, in storageInitialize
File "/usr/bin/anaconda", line 1097, in <module>
AttributeError: 'MultipathDevice' object has no attribute 'sysfs_path'
install exited abnormally [1/1]
The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete.
that's a separate and known issue, please retest with an updates image
containing a fix for that:
If you get an error please upload the traceback file.
patch fixing the issue sent to anaconda-devel-list.
I verified it is working against the RHEL6.0-20100804.n.0 tree.
*** Bug 595866 has been marked as a duplicate of this bug. ***
fixed by fb1d5c5d803eca156fb47ad83f66a6cfc149c0ca, will make it into anaconda-13.21.69-1.
Verified on RHEL6.0-20100809.0
Event posted on 08-23-2010 02:14pm EDT by Glen Johnson
------- Comment From firstname.lastname@example.org 2010-08-23 13:57 EDT-------
Verified this bug on RHEL6 Snap11 x86_64 on x3850 M2 system and issue did
not get reproduced.
Looks like anaconda version 13.21.78-1.el6 has fix for this issue.
[root@elm17d51 ~]# uname -a
Linux elm17d51.beaverton.ibm.com 2.6.32-63.el6.x86_64 #1 SMP Wed Aug 11
00:38:12 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
This event sent from IssueTracker by jkachuck
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.