Created attachment 933673 [details]
Description of problem:
I can't install rhevh, it's always stucked at 33 % of the installation and I see:
Exception: RuntimError('Failed to partition/format',) appers at 33 % of installation
and there also appears systemd output - [OK] Created slice user-0.slice.
This is super annoying especially because one doesn't get any other info - please consider to show some more text info from the installer on other console (like tail -f ...). Also please consider to make shell accessible on another console, there are only gettys there now which is useless...
The disk is not cleaned, that's true but I used 'firstboot' which should make it pass.
My configuration of pxe:
MENU LABEL ^interactive - rhevh-7.0-20140827.0.el7ev
APPEND rootflags=loop initrd=images/RHEVH/rhevh-7.0-20140827.0.el7ev/initrd0.img root=live:/rhevh-7.0-20140827.0.el7ev.iso rootfstype=auto ro rd.live.image rd.live.check rd.lvm=0 rd_NO_MULTIPATH rootflags=ro crashkernel=128M elevator=deadline install max_loop=256 rd.luks=0 rd.md=0 rd.dm=0 firstboot
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. not really idea, just netboot via pxe and have some mbr/partitions on the disk (although I tried to `dd' first 100 MB with /dev/zero and it didn't help)
should pass, force to wipe all mbr/partitions/whatever
Could it be that the disks you tried to install RHEV-H on contained a partition table or some filesystems?
IIRC I tried both with "dirty" disk and later with cleaned disk (dd if=/dev/zero...). Anyway I used 'firstboot' as kernel arg during boot which should make the installer to ignore anything on the disk.
Jiri, this bug should be duplicated of Bug 1095081 - Reinstalling rhevh7.0 hang on disk partitioning and creating file system [POST]
You can check your issue when new ovirt-node/rhevh will be built this week again.
And you need to boot the image using enforcing=0 because there are some SELinux
issues on such scratch build, you also need provide the audit.log.
This strongly appears to be a duplicate of 1095081, the root cause of which is a behavior change in LVM which prompts for input if it thinks you're trying to create an LV which has already existed.
According to comment 5 this seems to be a dupe of bug 1095081, moving this bug to ON_QA, a build will be named shortly.
*** This bug has been marked as a duplicate of bug 1095081 ***