Description of problem: I was installing RHEL6.0-Snapshot-7 on a system with a CCISS controller. The CCISS drive didn't show up under Firmware RAID where it belongs. It was under the multipath tab. If you selected the mpath device as the install target, the install failed leaving the attached trace info.
This is probably not an anaconda problem but it seems like the place to start.
Version-Release number of selected component (if applicable):
How reproducible: It was happening every time until I deleted the drives from the logical drive on the CCISS controller. On the next install, the drive showed up in the Firmware RAID tab.
Created attachment 432439 [details]
This is the trace I scp'ed to my system after the install failure.
Please attach the output of udevadm info --export-db to this bug report.
(In reply to comment #2)
> Please attach the output of udevadm info --export-db to this bug report.
The trace I attached is all the information I have.
09:38:11,492 INFO : Running... ['multipath', '-d']
09:38:11,788 INFO : create: mpatha (3600508b1001037383941424344450400) undef HP,LOGICAL VOLUME
09:38:11,788 INFO : size=137G features='0' hwhandler='0' wp=undef
09:38:11,788 INFO : `-+- policy='round-robin 0' prio=0 status=undef
09:38:11,789 INFO : |- 0:0:0:0 cciss!c0d0 104:0 undef faulty running
09:38:11,789 INFO : |- 0:0:1:0 cciss!c0d1 104:16 undef faulty running
09:38:11,789 INFO : `- 0:0:2:0 cciss!c0d2 104:32 undef faulty running
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. **
Reassigning this one to device-mapper-multipath for their input.
This looks like it's a dup of 592998. This was fixed in device-mapper-multipath-0.4.9-26.el6 (Snapshot 12). Could you please try upgrading and retesting.
Barry tested on the system were he first saw this issue (as reported in comment#0) and is no longer seeing this problem (tested multiple times with RC-4).
Closing as a dup of bug# 592998
*** This bug has been marked as a duplicate of bug 592998 ***