Proposing as a beta blocker:
"When using the custom partitioning flow, the installer must be able to reject or disallow invalid disk and volume configurations without crashing."
I'm going under the assumption that what the user did is invalid: retained the default vg/lv name for the new / of "fedora-root" which conflicts with existing. Installer shouldn't crash, but I suspect the work around is to name the root differently.

Update: When I do this with conventional LVM, the new root default name is root00 so the conflict with existing root doesn't occur. With LVM Thin Provisioning, the default name for root is root, so it conflicts with existing root.

(In reply to David Lehman from comment #20)
> (In reply to Chris Murphy from comment #12)
> > reason: DeviceCreateError: ('lvcreate failed for fedora/root:
> > running lvm lvcreate --thinpool fedora/pool00 --virtualsize 10000m -n root
> > failed', 'fedora-root')
>
> This is completely unrelated to the original bug in this report. Please open
> a separate report.
This bug was accepted as a blocker with the understanding that users would hit this bug if they installed over a previous lvm-using install due to name collisions. Are we correct in our understanding of how this bug would manifest?

Trying to install to a new LV using remaining space in VolGroup00. PV is on a software raid 10. Took several trips thru the custom partitioner before it saw the VG. All looked ok until setting root password, system froze for some unknown period of time as I had to leave for an appointment and upon return saw this error.
cmdline: /usr/bin/python /sbin/anaconda
cmdline_file: initrd=initrd.img inst.stage2=hd:UUID=223ac99f-66fa-45d6-a71d-2c5d282acab5 selinux=0 BOOT_IMAGE=vmlinuz
hashmarkername: anaconda
kernel: 3.11.6-301.fc20.x86_64
package: anaconda-20.25.6-1
product: Fedora
reason: DeviceCreateError: ('lvcreate failed for VolGroup00/fedora20: running lvm lvcreate -L 15968m -n fedora20 --config devices { filter=["r|/sdi1$|","r|/sdi$|","r|/sdh1$|","r|/sdh2$|","r|/sdh3$|","r|/sdh4$|","r|/sdh5$|","r|/sdh6$|","r|/sdh$|","r|/VolGroup01-clydehome$|","r|/VolGroup01-secondhome$|","r|/VolGroup01$|","r|/sde1$|","r|/sde10$|","r|/sde11$|","r|/sde12$|","r|/VolGroup03-rhel65beta$|","r|/VolGroup03-slackware$|","r|/VolGroup03-testhomes$|","r|/VolGroup03$|","r|/sde2$|","r|/sde3$|","r|/sde4$|","r|/sde5$|","r|/sde6$|","r|/sde7$|","r|/sde8$|","r|/sde9$|","r|/sde$|","r|/sdf1$|","r|/root06$|","r|/fedora_p5k-ewifi$|","r|/sdf10$|","r|/root07$|","r|/fedora_p5k-ewifi$|","r|/sdf11$|","r|/root08$|","r|/fedora_p5k-ewifi$|","r|/sdf12$|","r|/root09$|","r|/fedora_p5k-ewifi-brc4$|","r|/sdf13$|","r|/root10$|","r|/fedora_p5k-ewifi-brc5$|","r|/sdf14$|","r|/root$|","r|/fedora_p5k-ewifi$|","r|/sdf2$|","r|/root00$|","r|/fedora_p5k-ewifi$|","r|/sdf3$|","r|/root01$|","r|/fedora_new-host$|","r|/sdf4$|","r|/root02$|","r|/fedora_p5k-ewifi$|","r|/sdf5$|","r|/home$|","r|/opt$|","r|/srv$|","r|/tmp$|","r|/usr/local$|","r|/var/crash$|","r|/var/log$|","r|/var/opt$|","r|/var/spool$|","r|/var/tmp$|","r|/boot/grub2/x86_64-efi$|","r|/boot/grub2/i386-pc$|","r|/.snapshots$|","r|/.snapshots/1/snapshot$|","r|/.snapshots/2/snapshot$|","r|/.snapshots/3/snapshot$|","r|/.snapshots/4/snapshot$|","r|/.snapshots/5/snapshot$|","r|/.snapshots/6/snapshot$|","r|/.snapshots/7/snapshot$|","r|/.snapshots/8/snapshot$|","r|/.snapshots/9/snapshot$|","r|/.snapshots/10/snapshot$|","r|/.snapshots/11/snapshot$|","r|/.snapshots/12/snapshot$|","r|/.snapshots/13/snapshot$|","r|/.snapshots/14/snapshot$|","r|/.snapshots/15/snapshot$|","r|/.snapshots/16/snapshot$|","r|/.snapshots/17/snapshot$|","r|/.snapshots/18/snapshot$|","r|/.snapshots/19/snapshot$|","r|/.snapshots/20/snapshot$|","r|/.snapshots/21/snapshot$|","r|/.snapshots/22/snapshot$|","r|/.snapshots/23/snapshot$|","r|/.snapshots/24/snapshot$|","r|/.snapshots/25/snapshot$|","r|/.snapshots/26/snapshot$|","r|/.snapshots/27/snapshot$|","r|/.snapshots/28/snapshot$|","r|/.snapshots/29/snapshot$|","r|/suse_13-1_Beta-1$|","r|/sdf6$|","r|/root03$|","r|/fedora_p5k-ewifi$|","r|/sdf7$|","r|/root04$|","r|/fedora_p5k-ewifi$|","r|/sdf8$|","r|/root05$|","r|/fedora_new-host$|","r|/sdf9$|","r|/sdf$|"] } VolGroup00 failed', 'VolGroup00-fedora20')
release: Cannot get release name.
version: 20-Beta

For future reference, anytime anaconda crashes you need to retain the /tmp/anaconda-tb file so they can be manually attached. Only for new bugs does libreport upload them. (Maybe it should be an RFE for libreport to always upload just the anaconda-tb for subsequent reports for existing bugs?)

From what I remember:
1. I did a default install, but removed swap from the layout (therefore there has been some space left on the device, I don't know how much)
2. I started the installer again, and anaconda did not ask me to reclaim any space (as if there is enough already). I went to custom partitioning and found out that aconda created a new 500 MB /boot, 3.9 GB / and 3.9 GB swap. The previous partitions were left intact.
3. I accepted the choices and started the installation.
4. It crashed at the beginning of the installation process.
cmdline: /usr/bin/python /sbin/anaconda
cmdline_file: inst.repo=nfs:nfs.englab.brq.redhat.com:/pub/fedora/fedora-alt/stage/20-RC1/Fedora/i386/iso/Fedora-20-i386-DVD.iso initrd=F20/RC1/i386/initrd.img BOOT_IMAGE=F20/RC1/i386/vmlinuz
hashmarkername: anaconda
kernel: 3.11.10-301.fc20.i686
package: anaconda-20.25.15-1
product: Fedora
reason: DeviceCreateError: ('vgcreate failed for fedora_dhcp-28-168: running lvm vgcreate -s 4m --config devices { filter=["r|/sdb1$|","r|/sdb2$|","r|/sdc1$|","r|/sdb$|","r|/sdc$|"] } fedora_dhcp-28-168 /dev/sda5 failed', 'fedora_dhcp-28-168')
release: Cannot get release name.
version: 20

Steps I was doing to get comment 37:
1. Start with 3 empty 8gb disks.
2. Select all 3 disks in installation destination. Start custom partitioning with LVM.
3. Auto-create mount points.
4. Select /, press change for volume group. Select first two disks, change level to RAID-0. Click update.
5. Reduce / size to 5 G to make more space. Click update.
5. Select swap, reduce size to 500M to make more space.
6. Add /var, 1G size.
7. Add new volume group for /var, use RAID-1 for it and assign it only for 2nd and 3rd disks.
8. Add /home without size.
9. Switch /home VG to new VG.
Note this inconsistency:
10. Click on /var, click Change for volume group. Note that it has 1st and 2nd disks selected. Switch to 2nd and 3rd, save, update.
11. Start install.
Adding as blocker as per:
The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration.

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
of '21'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 21 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.
Thank you for reporting this bug and we are sorry it could not be fixed.

Note

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