Bug 832974 - auto-installation with BOOTIF=link fails because link is not detected
Summary: auto-installation with BOOTIF=link fails because link is not detected
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: unspecified
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Fabian Deutsch
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-18 10:01 UTC by Fabian Deutsch
Modified: 2016-04-26 17:09 UTC (History)
7 users (show)

Fixed In Version: 2.5.0
Clone Of:
Environment:
Last Closed: 2012-08-09 11:47:53 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)

Description Fabian Deutsch 2012-06-18 10:01:25 UTC 
Description of problem:
If selinux is enabled (and enforcing) ethtool will provide no output and thus the boot scripts can not determin the rgith interface to use in the case of BOOTIF=link.

Version-Release number of selected component (if applicable):
2.4.0-1.1

How reproducible:
always


Additional info:
After installation:
$ ethtool eth0
$ setenforce 0
$ ethtool eth0
... lots and lots of informations...
Comment 1 Fabian Deutsch 2012-06-18 14:51:39 UTC 
Maybe it was to early to blame selinux for this, it could also be bug #833088
Comment 2 Fabian Deutsch 2012-06-19 11:03:39 UTC 
The problem seemed to be that the interfaces need to be brought up before the link status can be checked with ethtool:

http://gerrit.ovirt.org/#/c/5450/
Comment 3 Fabian Deutsch 2012-06-19 11:18:18 UTC 
Tested as follows:
1. Build ISO with above patch
2. Append "BOOTIF=link storage_init=/dev/vda" in a VM booting that iso
3. Wait for auto install to finish
4. Boot into single mode in installed VM
5. Set admin password by running ovirt-config-password and reboot
6. Login to TUI and check network connectivity
= Correct/first connected NIC was choosen
Note You need to log in before you can comment on or make changes to this bug.