Bug 1150377

Created attachment 944888 [details]
attached ovirt.log

Snippet from the logs:

2014-10-08 09:11:13,110 - INFO - ovirtfunctions - Removing HostVG
2014-10-08 09:11:13,110 - INFO - ovirtfunctions - Wiping old boot sector
Error: Partition(s) on /dev/mapper/350024e920554256e are being used.
wipefs: invalid option -- 'f'
Usage: wipefs [options] <device>

Options:
 -a, --all           wipe all magic strings (BE CAREFUL!)
 -h, --help          this help
 -n, --no-act        everything to be done except for the write() call
 -o, --offset <num>  offset to erase, in bytes
 -p, --parsable      print out in parsable instead of printable format

For more information see wipefs(8).
2014-10-08 09:11:13,202 - DEBUG - ovirtfunctions - sync
2014-10-08 09:11:13,203 - DEBUG - ovirtfunctions - 
2014-10-08 09:11:13,222 - DEBUG - ovirtfunctions - kpartx -a '/dev/mapper/350024e920554256e'
2014-10-08 09:11:13,222 - DEBUG - ovirtfunctions - 
2014-10-08 09:11:13,473 - DEBUG - ovirtfunctions - partprobe
2014-10-08 09:11:13,473 - DEBUG - ovirtfunctions - 
2014-10-08 09:11:13,499 - DEBUG - ovirtfunctions - service multipathd reload
2014-10-08 09:11:13,499 - DEBUG - ovirtfunctions - Reloading multipathd: [60G[[0;32m  OK  [0;39m]

2014-10-08 09:11:14,259 - DEBUG - ovirtfunctions - multipath -r &>/dev/null
2014-10-08 09:11:14,259 - DEBUG - ovirtfunctions - 
2014-10-08 09:11:14,635 - DEBUG - ovirtfunctions - parted "/dev/mapper/350024e920554256e" -s "mkpart primary ext2 512M 768M"
2014-10-08 09:11:14,635 - DEBUG - ovirtfunctions - Error: You requested a partition from 512MB to 768MB.
The closest location we can manage is 320GB to 320GB.


So it seems that wipefs is taking different options, and thus does not erase remaining labels and fs remainings.
Which further prevents to create the necessary LVs.

Created attachment 945216 [details]
attached ovirt.log for rhev-hypervisor6-6.6-20141008.0.iso

Created attachment 945217 [details]
attached ovirt-node.log for rhev-hypervisor6-6.6-20141008.0.iso

Created attachment 945231 [details]
attached ovirt.log from /tmp of rhevh

Maybe the root cause happen in here from /tmp/ovirt.log:
2014-10-09 07:56:32,976 - DEBUG - install - 
    grub --device-map=/liveos/grub/device.map <<EOF
root (hd0,2)
setup --prefix=/grub (hd0)
EOF

2014-10-09 07:56:32,996 - DEBUG - install - 

    GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename.]
grub> root (hd0,2)
 Filesystem type is ext2fs, partition type 0x83
grub> setup --prefix=/grub (hd0)
 Checking if "/grub/stage1" exists... no

Error 15t: File not found
grub> 
2014-10-09 07:56:32,996 - ERROR - install - GRUB setup failed
2014-10-09 07:56:32,996 - ERROR - install - Grub Installation Failed

Haiyang, it seems as if there are some remaining partitions on the disk which is sued for installation.

Can you please try to clean up the disk manually and then install RHEV-H?

Hi,

Just for the record, I have reproduced this report.
- No previous partitions in the disk 
- Installation via CDROM

In bug description, there are two additional scenario:
> Additional info:
> Also Provide two test scenarios for this iso.
> 1. TUI install RHEV-H with USB livecd with/without enforcing=0 ---
> Failed.(Exception: OSError(30,'Read-only file system') )
> 2. Auto install via PXE-- Failed.


Hey haiyang, how about these scenario on comment 15 builds?

(In reply to Ying Cui from comment #17)
> In bug description, there are two additional scenario:
> > Additional info:
> > Also Provide two test scenarios for this iso.
> > 1. TUI install RHEV-H with USB livecd with/without enforcing=0 ---
> > Failed.(Exception: OSError(30,'Read-only file system') )
> > 2. Auto install via PXE-- Failed.
> 
> 
> Hey haiyang, how about these scenario on comment 15 builds?

1. Auto install via pxe--suceess
2. TUI install RHEV-H with USB livecd/cdrom sometimes still failed with Exception: OSError(30,'Read-only file system') 

For scenario 2, I will report a new bug to track OSError exception issue.

(In reply to haiyang,dong from comment #18)
> 
> 1. Auto install via pxe--suceess
> 2. TUI install RHEV-H with USB livecd/cdrom sometimes still failed with
> Exception: OSError(30,'Read-only file system') 
> 
> For scenario 2, I will report a new bug to track OSError exception issue.

I have reported a new Bug 1152483 to track scenario 2 issue.

Created attachment 949236 [details]
attached ovirt-node.log

Test version:
rhev-hypervisor6-6.6-20141021.0.el6ev.noarch.rpm
ovirt-node-3.0.1-19.el6.18.noarch

scenario 1: clean disk and install rhev-hypervisor6-6.6-20141021.0.el6ev
 --Install failed and throw execption:
2014-10-22 02:47:15,721      ERROR Installer transaction failed
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ovirt/node/installer/core/progress_page.py", line 126, in __run
  File "/usr/lib/python2.6/site-packages/ovirt/node/plugins.py", line 234, in dry_or
  File "/usr/lib/python2.6/site-packages/ovirt/node/installer/core/progress_page.py", line 120, in do_commit
  File "/usr/lib/python2.6/site-packages/ovirt/node/installer/core/progress_page.py", line 280, in commit
RuntimeError: Failed to set install bootloader

scenario 2:install rhev-hypervisor6-6.6-20141021.0.el6ev on dirty disk-- Hanging on 40% of installation.

Created attachment 949237 [details]
attached logs for rhev-hypervisor6-6.6-20141021.0.el6ev iso

This bug can reproduce on rhevh 6.6 for 3.4.z build, so block QE testing now.

(In reply to haiyang,dong from comment #21)
> Created attachment 949237 [details]
> attached logs for rhev-hypervisor6-6.6-20141021.0.el6ev iso

I do not know if this was an auto-install or TUI install.
I also do not see if it was for scenario 1 or 2. I can just guess.

(In reply to Fabian Deutsch from comment #24)
> (In reply to haiyang,dong from comment #21)
> > Created attachment 949237 [details]
> > attached logs for rhev-hypervisor6-6.6-20141021.0.el6ev iso
> 
> I do not know if this was an auto-install or TUI install.
> I also do not see if it was for scenario 1 or 2. I can just guess.

It's TUI install of scenario 1. Due to Hanging on 40% of installation for scenario 2, so i couldn't get any logs for scenario 2.

Steps to reproduce the issue in a VM:

1. _Install_ RHEV-H with:
qemu-img create -f qcow2 "hd1.qcow2" 30G
qemu-kvm \
  -serial stdio -m 2048 -boot d \
  -drive file=hd1.qcow2,media=disk,index=1,if=scsi,cache=none,serial=35000cca35fdc2dfc1 \
  -drive file=hd1.qcow2,media=disk,index=3,if=scsi,cache=none,serial=35000cca35fdc2dfc1 \
  -cdrom rhev-hypervisor6-6.6-20141024.0.iso

2. Reboot right after installation
3. Choose _Reinstall_ and do the TUI renistall
4. The installation hangs at 40%

Test version:
rhevh-6.6-20141119.0.el6ev.iso
ovirt-node-3.1.0-0.27.20141119git24e087e.el6.noarch

Didn't meet it in my physical machine, so this bug has been fixed in in rhevh 6.6 for RHEV 3.5 bulid version, change the status into "VERIFIED"

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-0160.html