Created attachment 933762 [details] screenshot 1 Description of problem: _drive_size ValueError and /usr/libexec/ovirt-functions: line 1121: plymouth: command not found, see screenshot. pxe conf used for booting MENU LABEL ^auto - rhevh-7.0-20140827.0.el7ev KERNEL images/RHEVH/rhevh-7.0-20140827.0.el7ev/vmlinuz0 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 max_loop=256 rd.luks=0 rd.md=0 rd.dm=0 firstboot install storage_init=ata storage_vol=::::: ssh_pwauth=1 adminpw=$1$a0gLYJ6j$N2cLwUuWx5o5dgVnD7M9L/ rhevm_admin_password=$1$a0gLYJ6j$N2cLwUuWx5o5dgVnD7M9L/ ntp=10.34.32.125 syslog=10.34.60.239 qemu_pxe=gpxe IPAPPEND 2 the disk is 'sda', see screenshot for storag details. Version-Release number of selected component (if applicable): rhevh-7.0-20140827.0.el7ev How reproducible: ??? Steps to Reproduce: 1. it just happens on my dell-r210ii-04 2. 3. Actual results: i can't install this rhevh on dell r210ii for hours :/ Expected results: it should be piece of cake Additional info:
Created attachment 933763 [details] screenshot 2
Did the disk have a partition table or a filesystem on it?
(In reply to Jiri Belka from comment #0) > Created attachment 933762 [details] > screenshot 1 > > Description of problem: > _drive_size ValueError and /usr/libexec/ovirt-functions: line 1121: > plymouth: command not found, see screenshot Howdy Jiri, For plymouth issue we have already a patch on gerrit: http://gerrit.ovirt.org/#/c/32025/ The rest of report I am going to try a reproducer and understand the output you provided.
I suppose there's partition tables etc... but I used 'firstboot' as kernel arg.
Hi jbelka, I can reproduce the plymouth issue on build rhevh-7.0-20140827.0.el7ev, but didn't met another issue "ValueError: invalid literal for init() with base 10" which like attachment show. Maybe it is related with hard disk type. Can you 100% reproduce this bug? Did you met this issue on other machine? Or it just occurs on dell-r210ii-04? NOTE: Please boot the image using enforcing=0 because there are some SELinux issue with the first few rhevh7.0 builds. Auto clean install can successful in my side(with enforcing=0). Thanks!
> Can you 100% reproduce this bug? I wrote on comment #0 '???', so no always, I just got it. > Did you met this issue on other machine? Or it just occurs on dell-r210ii-04? As I can't reproduce easily and I haven't seen it on other machine. I tried auto install couple of times and it gets stucked on 0/2 step - partitioning/formating. I tried both with cleaned disk and with the disk being already partitioned and having HostVG. I can't provide more info.
(In reply to Jiri Belka from comment #6) > > Can you 100% reproduce this bug? > > I wrote on comment #0 '???', so no always, I just got it. > > > Did you met this issue on other machine? Or it just occurs on dell-r210ii-04? > > As I can't reproduce easily and I haven't seen it on other machine. > > I tried auto install couple of times and it gets stucked on 0/2 step - > partitioning/formating. I tried both with cleaned disk and with the disk > being already partitioned and having HostVG. > humm, I think I have reproduced this report. I have used auto-install with 15G of HD in a virtual machine, not always but happened once. Jiri, if you keep pressing F2 to go to console "before the stuck" is it possible to collect /var/log/ovirt* logs?
pressing F2 did nothing in my case.
Created attachment 934085 [details] /var/log & /tmp in archive If you need access I can give you access to dell idrac :D
Info to #9 - this time it finished in a state when it asked to press 's' to drop to shell, thus no installer at all.
> I can reproduce the plymouth issue on build rhevh-7.0-20140827.0.el7ev, but > didn't met another issue "ValueError: invalid literal for init() with base > 10" which like attachment show. > Maybe it is related with hard disk type. > Shao Chen, can we reproduce this ValueError on our machines now?
(In reply to Ying Cui from comment #11) > > I can reproduce the plymouth issue on build rhevh-7.0-20140827.0.el7ev, but > > didn't met another issue "ValueError: invalid literal for init() with base > > 10" which like attachment show. > > Maybe it is related with hard disk type. > > > > Shao Chen, can we reproduce this ValueError on our machines now? I tested the bug on our dell r210 machine and some Vms many times, I just can reproduce the plymouth issue, but still can't reproduce the ValueError. Hi Jiri Belka, I can't reproduce the valueError issue with our ENV, could you help us to verify this bug after fix the issue? Thanks!
I can reproduce without problem. If you have problem to reproduce on your hw please contact me to get access to my hw (it has IPMI).
Created attachment 938823 [details] again 1
Created attachment 938824 [details] again 2
Created attachment 938825 [details] again 3
(In reply to Jiri Belka from comment #13) > I can reproduce without problem. If you have problem to reproduce on your hw > please contact me to get access to my hw (it has IPMI). Hi Jiri Belka, Thanks for share the new attachment, it is very useful. I can reproduce the valueError issue now. I guess the keyword should be "storage-init=ata". if user append ata to cmd on a physical machine(but not VMs), then the bug could be easy to reproduce. Test version: rhevh-7.0-20140827.0.el7ev @ycui, please add qa_ack+ flag. Thanks!
Please provide the logfiles, at best all of /var/log
this BZ is chaos, closing as duplicate of BZ1163688 which is more clear that it is related to storage_init=ata. *** This bug has been marked as a duplicate of bug 1163688 ***