RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 959957 - Auto install RHEV-H with "BOOTIF=link" parameter, it will enter tui install process not auto install process .
Summary: Auto install RHEV-H with "BOOTIF=link" parameter, it will enter tui install p...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.4
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: rc
: ---
Assignee: Fabian Deutsch
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-06 09:59 UTC by haiyang,dong
Modified: 2014-01-21 19:33 UTC (History)
13 users (show)

Fixed In Version: ovirt-node-3.0.1-7.el6
Doc Type: Bug Fix
Doc Text:
Previously for automatic installation, the link state of a device was determined in one pass. This could lead to problems when the hardware took several minutes to initialize, or set the link state to UP. Now five passes are allowed to find a device with a link before it falls back to the TUI installation.
Clone Of:
Environment:
Last Closed: 2014-01-21 19:33:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0033 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2014-01-22 00:14:30 UTC
oVirt gerrit 20503 0 None None None Never

Description haiyang,dong 2013-05-06 09:59:25 UTC 
Description of problem:
Auto install RHEV-H with the follow parameter:
BOOTIF=link storage_init=/dev/sda firstboot

actually, it will enter tui manual install process not auto install process 
can reproduce this issue on physical machine's nic named "ethx" or "emx".
May the root cause happen in the follow code of /usr/libexec/ovirt-init-functions.sh:
    404                 link)
    405                 for eth in $(cd /sys/class/net; echo [ep]*); do
    406                     ip link set dev $eth up
    407                     if ethtool $eth 2>/dev/null|grep -q "Link detected:         yes"        
    408                     then
    409                         bootif=$eth
    410                         break
    411                     fi
    412                 done

Append "sleep 5" after line 406 can resole this issue:
    404                 link)
    405                 for eth in $(cd /sys/class/net; echo [ep]*); do
    406                     ip link set dev $eth up
    407                     sleep 5
    408                     if ethtool $eth 2>/dev/null|grep -q "Link detected:         yes"        
    409                     then
    410                         bootif=$eth
    411                         break
    412                     fi
    413                 done


Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20130501.0.el6_4

How reproducible:
100% 
 
Steps to Reproduce:
1.Auto install RHEV-H with the follow parameter:
BOOTIF=link storage_init=/dev/sda firstboot

Actual result:          
                                                  
Expect result:
Auto install RHEV-H successfully with "BOOTIF=link" parameter

Additional info:
Comment 2 Fabian Deutsch 2013-09-18 08:32:58 UTC 
(In reply to haiyang,dong from comment #0)
> Append "sleep 5" after line 406 can resole this issue:
>     404                 link)
>     405                 for eth in $(cd /sys/class/net; echo [ep]*); do
>     406                     ip link set dev $eth up
>     407                     sleep 5
>     408                     if ethtool $eth 2>/dev/null|grep -q "Link
> detected:         yes"        
>     409                     then
>     410                         bootif=$eth
>     411                         break
>     412                     fi
>     413                 done

I understand the solution. The problem I see is that it depends on the driver and hardware how long it takes until the device appears as up.

Can you provide which NIC hardware and driver was used?
Comment 3 haiyang,dong 2013-09-18 09:09:10 UTC 
(In reply to Fabian Deutsch from comment #2)
> (In reply to haiyang,dong from comment #0)
> I understand the solution. The problem I see is that it depends on the
> driver and hardware how long it takes until the device appears as up.
> 
> Can you provide which NIC hardware and driver was used?

[root@dhcp-9-31 admin]# lspci |grep "Ethernet"
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
[root@dhcp-9-31 admin]# ls /sys/class/net/em1/device/driver/module -l
lrwxrwxrwx. 1 root root 0 2013-09-18 09:07 /sys/class/net/em1/device/driver/module -> ../../../../module/e1000e
Comment 4 Fabian Deutsch 2013-09-18 16:23:37 UTC 
Thanks.

Mike,

shall we just 
1) add one sleep (which might not help always)
2) shall loop a couple of times combined with sleep
3) loop and prompt the user now and then to stop polling?
4) other ideas?

I'd tend to use (2). 10 loops each with a 5sec sleep.

Fix would be to monitor the state change of the nic. Could work with `ip monitor`, but that might be problematic if it never comes up.
Comment 5 Mike Burns 2013-09-19 12:38:23 UTC 
I would loop 5 times with 1 sec wait *only* if it's "link"  If it's not up in that time frame, log a message and proceed to the tui.
Comment 7 haiyang,dong 2013-10-20 09:20:41 UTC 
Test version:
rhev-hypervisor6-6.5-20131017.0.iso
ovirt-node-3.0.1-4.el6

Auto install RHEV-H with the follow parameter:
BOOTIF=link storage_init=/dev/sda firstboot

actually, it still enter tui manual install process not auto install process 

so this bug wasn't fixed, need to re-assigned it again.
Comment 8 haiyang,dong 2013-11-01 03:00:46 UTC 
Test version:
rhevh-6.5-20131031.1.0.iso
ovirt-node-3.0.1-7.el6

Auto install RHEV-H with the follow parameter:
BOOTIF=link storage_init=/dev/sda firstboot

Auto install RHEV-H successfully with "BOOTIF=link" parameter

so this bug has been fixed, after the status of this bug change into "ON_QA", i will verify it.
Comment 9 haiyang,dong 2013-11-01 12:34:53 UTC 
According to comment 8, change the status of this bug into "VERIFIED"
Comment 11 errata-xmlrpc 2014-01-21 19:33:06 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2014-0033.html
Note You need to log in before you can comment on or make changes to this bug.