Description of problem:
I created a vm machine with qemu to simulate multpath access on 2 different empty disks. 
I installed fedora 24 on first empty disk without any problem.
I know that it is not possible to install again a fedora on this same disk as it is not anymore empty (https://bugzilla.redhat.com/show_bug.cgi?id=1274392) but I tried to install a new fedora on the second empty disk.
This is failling too (this bug). 

Note that this problem is reproductable on bare metal machine with multipath disks.

qemu command:
/usr/bin/qemu-system-ppc64 -name f24_test -enable-kvm -M pseries -smp 4 -m 4G -nographic -nodefaults -monitor stdio -serial pty -device virtio-net-pci,netdev=net10132,mac=c0:ff:ee:00:00:92 -netdev bridge,br=br0,id=net10132 -device virtio-scsi-pci,id=scsi -drive if=none,id=hda,file=hd1.qcow2,serial=0002 -device scsi-hd,drive=hda -drive if=none,id=hdb,file=hd1.qcow2,serial=0002 -device scsi-hd,drive=hdb -drive if=none,id=hdc,file=hd2.qcow2,serial=0003 -device scsi-hd,drive=hdc -drive if=none,id=hdd,file=hd2.qcow2,serial=0003 -device scsi-hd,drive=hdd -cdrom isole -boot d -S

here is info after first success install.
blkid
/dev/sr0: UUID="2016-03-17-08-38-47-00" LABEL="Fedora-S-dvd-ppc64le-24" TYPE="iso9660" PTTYPE="dos"
/dev/sda: PTUUID="c901093a" PTTYPE="dos"
/dev/sdc: UUID="eade29ce-d65f-4050-9c4b-c59e2456f19d" TYPE="ext4"
/dev/sdb: PTUUID="c901093a" PTTYPE="dos"
/dev/mapper/mpatha: PTUUID="c901093a" PTTYPE="dos"
/dev/sdd: UUID="eade29ce-d65f-4050-9c4b-c59e2456f19d" TYPE="ext4"
/dev/mapper/mpatha1: PARTUUID="c901093a-01"
/dev/mapper/mpatha2: UUID="d0d460c8-4df1-4491-8ed2-5f988cf84f11" TYPE="ext4" PARTUUID="c901093a-02"
/dev/mapper/mpatha3: UUID="mjnXpV-s9Be-RWLV-j2dT-EN7K-QDRU-rfdphw" TYPE="LVM2_member" PARTUUID="c901093a-03"
/dev/mapper/fedora_vm92-root: UUID="2243e2d0-c12d-48c2-912d-4f8ea05b3f51" TYPE="xfs"
/dev/mapper/fedora_vm92-swap: UUID="7e8002b6-522a-44c7-bd30-5cc4bc22f258" TYPE="swap"
/dev/mapper/mpathb: UUID="eade29ce-d65f-4050-9c4b-c59e2456f19d" TYPE="ext4"

pvdisplay
  --- Physical volume ---
  PV Name               /dev/mapper/mpatha3
  VG Name               fedora_vm92
  PV Size               19.51 GiB / not usable 3.00 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              4993
  Free PE               0
  Allocated PE          4993
  PV UUID               mjnXpV-s9Be-RWLV-j2dT-EN7K-QDRU-rfdphw

vgdisplay
  --- Volume group ---
  VG Name               fedora_vm92
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  3
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                2
  Open LV               2
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               19.50 GiB
  PE Size               4.00 MiB
  Total PE              4993
  Alloc PE / Size       4993 / 19.50 GiB
  Free  PE / Size       0 / 0   
  VG UUID               0blUoQ-VKYq-BCET-21xt-rxjv-XFxo-FI4o5r

It seems that on second install, system tries to create the fix named vg "fedora_vm92" (vm92 is the hostname) but
this vg already exists on the first disk...



Version-Release number of selected component:
anaconda-24.13-1

The following was filed automatically by anaconda:
anaconda 24.13-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python3.5/site-packages/gi/overrides/BlockDev.py", line 416, in wrapped
    raise transform[1](msg)
  File "/usr/lib/python3.5/site-packages/blivet/devices/lvm.py", line 234, in _create
    blockdev.lvm.vgcreate(self.name, pv_list, self.peSize)
  File "/usr/lib/python3.5/site-packages/blivet/devices/storage.py", line 457, in create
    self._create()
  File "/usr/lib/python3.5/site-packages/blivet/deviceaction.py", line 312, in execute
    self.device.create()
  File "/usr/lib/python3.5/site-packages/blivet/actionlist.py", line 280, in process
    action.execute(callbacks)
  File "/usr/lib/python3.5/site-packages/blivet/devicetree.py", line 381, in processActions
    callbacks=callbacks)
  File "/usr/lib/python3.5/site-packages/blivet/blivet.py", line 164, in doIt
    self.devicetree.processActions(callbacks=callbacks)
  File "/usr/lib/python3.5/site-packages/blivet/osinstall.py", line 1096, in turnOnFilesystems
    storage.doIt(callbacks)
  File "/usr/lib64/python3.5/site-packages/pyanaconda/install.py", line 195, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg)
  File "/usr/lib64/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.5/site-packages/pyanaconda/threads.py", line 253, in run
    threading.Thread.run(self, *args, **kwargs)
gi.overrides.BlockDev.LVMError: Process reported exit code 768:   /dev/fedora_vm92: already exists in filesystem
  Run `vgcreate --help' for more information.


Additional info:
addons:         com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=/ppc/ppc64/vmlinuz ro
dnf.rpm.log:    Mar 23 15:03:35 INFO --- logging initialized ---
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.5.0-0.rc7.git0.2.fc24.ppc64le
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        24