Red Hat Bugzilla – Bug 831668
network is not brought up when run in a VM with multiple NICs
Last modified: 2016-04-26 10:12:15 EDT
Description of problem:
An autoinstall using firstboot and BOOTIF=eth0 (eth0 exists) doesn't bring up networking.
This could already be broken in 2.3.0
Version-Release number of selected component (if applicable):
The network cards are named differently on firstboot and after the installation.
Ths ifcfg scripts contain a wrong dev/mac mapping.
In a multi NIC setup, the order of NICs is unstable on F17 based installs but just if biosdevname is not actiavted/working.
This is the case for VMs, where biosdevname is deactivated so that - if multiple NICs are assigned - their order can change between reboots.
(a) bug #824595 would help to solve this problem.
(b) Alternatively it could help if the hypervisor provides enough informations about the nics for biosdevname which was talked about in bug #669955
If the problem exists just in this corner case (Node in a VM) we should push this into the future, as it is not relevant in practice, except when doing automated testing.
This seems to be fixed by bug #824595
Tested as follows:
1. Install a recent node with patch from given bug and the additional kargs BOOTIF=eth0 storage_init firstboot
2. After reboot, log in to the TUI
3. Check that the network is up (IP address given)
Fixed with bug #824595