Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1332326

Summary: Attempted LVM on software RAID over LVM on software RAID install crashes (infinite recursion?)
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 24CC: anaconda-maint-list, g.kaviyarasu, jonathan, pschindl, robatino, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-03 07:59:50 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:
Bug Depends On:    
Bug Blocks: 1230433    
Attachments:
Description Flags
storage.log
none
anaconda.log
none
program.log none

Description Adam Williamson 2016-05-02 23:27:55 UTC 
To reproduce:

1. Take a normal VM, attach two virtio disks
2. Boot from F24 Beta 1.4 Server netinst
3. Select both disks, go to custom part
4. Create a default LVM layout then change the LVM volume's backing from standard partitions to RAID-0
5. Complete the install
6. Reboot back to the installer
7. Select both disks, go to custom part
8. Delete both existing devices (the LVM volume and the /boot partition)
9. Create the same layout again (as in step 4)
10. Attempt to run the installation

For me, anaconda suddenly black screened during the partitioning phase. On ctrl-alt-f1 I could see 'pane is dead' and what looks like the end of a backtrace. From storage.log , it looks like there's some kind of infinite recursion going on.
Comment 1 Adam Williamson 2016-05-02 23:28:58 UTC 
Created attachment 1153091 [details]
storage.log
Comment 2 Adam Williamson 2016-05-02 23:30:22 UTC 
Created attachment 1153094 [details]
anaconda.log
Comment 3 Adam Williamson 2016-05-02 23:32:16 UTC 
Created attachment 1153095 [details]
program.log
Comment 4 Adam Williamson 2016-05-02 23:38:47 UTC 
I also hit this same bug for firmware RAID, with the following steps:

1. Start with a RAID-0 'Volume0' set, that hit https://bugzilla.redhat.com/show_bug.cgi?id=1332321
2. Go to the firmware interface, destroy that set
3. Create a new RAID-1 set called 'Volume1'
4. Do a default install of F24 Beta 1.4 Server (netinst) to that set (all works fine)
5. Reboot to the installer and try to do a default install over that fresh install (using the guided 'reclaim space' dialog to delete all contents of the set)

Proposing as a Beta blocker, seems to be a conditional violation of "The installer must be able to detect and install to hardware or firmware RAID storage devices" in the case of installing over an existing FW RAID install and of "When using the custom partitioning flow, the installer must be able to: ... Correctly interpret, and modify as described below, any disk with a valid ms-dos or gpt disk label and partition table containing ext4 partitions, LVM and/or btrfs volumes, and/or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions ... Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes, or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions" in the case of installing over an existing SW RAID install...
Comment 5 Petr Schindler 2016-05-03 07:59:50 UTC 

*** This bug has been marked as a duplicate of bug 1331630 ***