Bug 1136392

Summary: [rhevh][el7] _drive_size ValueError and /usr/libexec/ovirt-functions: line 1121: plymouth: command not found
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: ovirt-nodeAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 3.5.0CC: cshao, ecohen, fdeutsch, gklein, hadong, huiwa, iheim, jbelka, leiwang, lsurette, pstehlik, rbarry, tlitovsk, yaniwang, ycui, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-13 10:44:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1094719    
Attachments:
Description Flags
screenshot 1
none
screenshot 2
none
/var/log & /tmp in archive
none
again 1
none
again 2
none
again 3 none

Description Jiri Belka 2014-09-02 13:28:52 UTC
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:

Comment 1 Jiri Belka 2014-09-02 13:29:18 UTC
Created attachment 933763 [details]
screenshot 2

Comment 2 Fabian Deutsch 2014-09-02 16:43:20 UTC
Did the disk have a partition table or a filesystem on it?

Comment 3 Douglas Schilling Landgraf 2014-09-02 17:25:38 UTC
(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.

Comment 4 Jiri Belka 2014-09-03 07:04:54 UTC
I suppose there's partition tables etc... but I used 'firstboot' as kernel arg.

Comment 5 cshao 2014-09-03 10:02:06 UTC
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!

Comment 6 Jiri Belka 2014-09-03 12:12:45 UTC
> 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.

Comment 7 Douglas Schilling Landgraf 2014-09-03 12:20:36 UTC
(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?

Comment 8 Jiri Belka 2014-09-03 12:26:40 UTC
pressing F2 did nothing in my case.

Comment 9 Jiri Belka 2014-09-03 13:05:40 UTC
Created attachment 934085 [details]
/var/log & /tmp in archive

If you need access I can give you access to dell idrac :D

Comment 10 Jiri Belka 2014-09-03 13:07:14 UTC
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.

Comment 11 Ying Cui 2014-09-17 07:00:48 UTC
> 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?

Comment 12 cshao 2014-09-18 05:36:44 UTC
(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!

Comment 13 Jiri Belka 2014-09-18 09:43:35 UTC
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).

Comment 14 Jiri Belka 2014-09-18 09:43:53 UTC
Created attachment 938823 [details]
again 1

Comment 15 Jiri Belka 2014-09-18 09:44:09 UTC
Created attachment 938824 [details]
again 2

Comment 16 Jiri Belka 2014-09-18 09:44:23 UTC
Created attachment 938825 [details]
again 3

Comment 17 cshao 2014-09-18 10:13:26 UTC
(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!

Comment 18 Fabian Deutsch 2014-11-06 15:59:22 UTC
Please provide the logfiles, at best all of /var/log

Comment 19 Jiri Belka 2014-11-13 10:44:38 UTC
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 ***