Bug 591257 - anaconda thinks HP MSA2000 FC attached storage is Simple Storage
Summary: anaconda thinks HP MSA2000 FC attached storage is Simple Storage
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Peter Jones
QA Contact: Release Test Team
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-11 18:32 UTC by Barry Marson
Modified: 2010-11-10 19:43 UTC (History)
2 users (show)

Fixed In Version: anaconda-13.21.40-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-11-10 19:43:19 UTC
Target Upstream Version:

Attachments (Terms of Use)
storage.log (239.29 KB, text/plain)
2010-05-11 20:35 UTC, Barry Marson
no flags Details
storage.log from advanced selection (238.99 KB, text/x-log)
2010-05-12 15:50 UTC, Barry Marson
no flags Details

Description Barry Marson 2010-05-11 18:32:24 UTC
Description of problem:

I have to keep Simple storage selected to install an OS on HP MSA2000 based storage.  This storage is FC attached.

Version-Release number of selected component (if applicable):
RHEL6.0-20100506.3 but has been a problem at least as far back as distros from early march.

How reproducible:
every time

Steps to Reproduce:
1. have to select Simple to get FC based storage to show up
Actual results:

Expected results:

Additional info:

Comment 2 Chris Lumens 2010-05-11 20:24:53 UTC
Can you attach /tmp/storage.log after running through and selecting advanced?

Comment 3 RHEL Program Management 2010-05-11 20:31:26 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 4 Barry Marson 2010-05-11 20:35:55 UTC
Created attachment 413253 [details]

as requested.

Comment 5 Barry Marson 2010-05-11 20:36:58 UTC
scratch that ... #4 is with simple storage

Comment 6 Barry Marson 2010-05-11 20:39:21 UTC
I do know that 2 months when I played with Advanced, my MSA storage LUNS didn't show up on the list.  I will have to try Advanced tomorrow.


Comment 7 Barry Marson 2010-05-12 15:50:17 UTC
Created attachment 413466 [details]
storage.log from advanced selection

I have other logs as well.

But I was surprised to find the MSA storage reported in both Simple and Advanced.


Comment 8 Chris Lumens 2010-05-12 20:00:39 UTC
I take it all your multipath devices are showing up in both the simple storage UI and in the advanced storage UI, right?  Which tab on the advanced storage UI are they showing up in?  Hopefully, the multipath tab.

I may need to come down and check this out in person tomorrow or Friday.

Comment 9 Chris Lumens 2010-05-13 15:12:27 UTC
pjones has patches on anaconda-maint-list that have been tested and make this work.

Comment 10 Chris Lumens 2010-05-13 15:31:47 UTC
Could we get a QA ack on this bug?  It's tested, approved, and ready to go.

Comment 12 Chris Lumens 2010-05-13 15:49:14 UTC

Comment 14 Alexander Todorov 2010-07-19 14:30:09 UTC
which system has this kind of storage? I wasn't able to find one in Beaker. Can you give QE access to the system or test again with snapshot #7 (snap #8 has bug #615936 when selecting Advanced storage).

Comment 15 Barry Marson 2010-07-20 14:58:57 UTC
Im not free to give up my machine, I will test snap 7.


Comment 16 Alexander Todorov 2010-07-21 16:09:58 UTC
setting needinfo from your for tracking purposes. Please provide test results when you finish testing snap #7 or newer snapshot.


Comment 17 Barry Marson 2010-07-27 21:25:57 UTC
Actually tested  RHEL6.0-20100722.0 and verified through the gui install that advanced device discovery shows the the correct luns in the correct tabs .. ie simple/advanced.  Of course I looked in the one that had SAN on it and when it wasnt there realized it was in multipath devices ...

So thumbs up.

Comment 18 releng-rhel@redhat.com 2010-11-10 19:43:19 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.