Bug 966874

Summary: traceback when multipath iscsi device
Product: [Fedora] Fedora Reporter: Jan Ščotka <jscotka>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, bcl, dlehman, dshea, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-20.3-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-02 19:36:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ana log
none
tb 1
none
tb 2
none
storage log none

Description Jan Ščotka 2013-05-24 07:38:53 UTC 
Description of problem:
Hi,
as participant of https://fedoraproject.org/wiki/Test_Day:2013-05-21_AnacondaNewUI_Followup#Advanced_Storage
I've tried installation on iscsi discs.
I have simulation via target utils (F19) created iscsi disc
  30 x disc
   via 2 path (2x multipath)

and it traceback with message:
Atribute Error: 'Multipath device' object has no atribute 'isMagic' - anaconda
due to F19 problem with reporting bugs directly I'm unable to report full  bug report

    Thansk&Regards
    Honza
Comment 2 Jan Ščotka 2013-05-24 07:52:46 UTC 
Hi,
I forgot to mention, that discs was probably properly detected via anaconda. I was able to see all discs. It failed when I tried to select partitoning (in my case lots of disc I selected custom partitioning)
Comment 3 Jan Ščotka 2013-05-24 08:07:30 UTC 
Created attachment 752492 [details]
ana log
Comment 4 Jan Ščotka 2013-05-24 08:08:07 UTC 
Created attachment 752493 [details]
tb 1
Comment 5 Jan Ščotka 2013-05-24 08:08:38 UTC 
Created attachment 752494 [details]
tb 2
Comment 6 Jan Ščotka 2013-05-24 08:24:17 UTC 
Created attachment 752497 [details]
storage log
Comment 7 David Lehman 2013-05-24 21:13:15 UTC 
What I see happening is the iscsi devices are added in two batches, each of which contains one path to each of the multipaths. When the first batch appears, the multipath tools tell us they are not multipath components (makes sense to some extent given that there is only one path to each at that point). When the second batch appears they are identified correctly as multipath components and the multipaths are activated correctly. The problem is that anaconda/blivet thinks the disks from the first batch are regular disks that can be manipulated directly, which leads to this crash.