Bug 1394565

Summary:	on_boot for one of the nic is set to no for RHV-H ISO installation
Product:	Red Hat Enterprise Linux 7	Reporter:	RamaKasturi <knarra>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	fdeutsch, rvykydal, sasundar, yturgema
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-16 15:06:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RamaKasturi 2016-11-13 16:18:17 UTC

Description of problem:
During RHV-H installation as part of network configuration i configure two nics. Once installation is completed i see that only one nic is up and another nic has on_boot set to no.

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


How reproducible:
Always

Steps to Reproduce:
1. Download RHV-H ISO from access.redhat.com
2. Try installing it on a hypervisor which has two nics
3. During network selection, configure both the nics

Actual results:
Once the installation is done i see that only one of the nic is up and another nic has on_boot set to no in the network config files.

Expected results:
When both the nics are configured during installation using anaconda, both the nics should have on_boot=yes and they should be functional.

Additional info:

Comment 1 Fabian Deutsch 2016-11-13 21:03:32 UTC

Yuval, can you reproduce this issue?

Comment 2 Yuval Turgeman 2016-11-14 09:02:29 UTC

(In reply to Fabian Deutsch from comment #1)
> Yuval, can you reproduce this issue?

Yes, reproduced on ovirt-node-ng-installer-master-2016110504.iso:

[root@localhost ~]# grep -i onboot /etc/sysconfig/network-scripts/ifcfg-e*
/etc/sysconfig/network-scripts/ifcfg-ens4:ONBOOT=no
/etc/sysconfig/network-scripts/ifcfg-eth0:ONBOOT="yes"

Comment 3 Radek Vykydal 2016-11-14 10:10:29 UTC

As noted also in the Installation Guide:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Installation_Guide/index.html#sect-edit-network-connections-x86

If you expect ONBOOT=yes for device configured in GUI you need to change the "no" default (NM Connection Editor - "Configure" -> "General" tab -> check "Automatically connect...").

Installer policy (based on behavior expected by a number of bug reports) is to automatically set ONBOOT="yes" for a single device activated during installation (as in your case), choosing the device with default route in case more devices were activated. That is why one of your devices configured in GUI have ONBOOT=yes set.

Comment 5 Fabian Deutsch 2016-11-16 14:12:34 UTC

Radek, this configuration has to be done after installation, in the control-center, right?

Comment 6 Radek Vykydal 2016-11-16 14:58:11 UTC

No, it can be done (as described in comment #3) right when configuring the device in installer GUI.

Comment 7 Fabian Deutsch 2016-11-16 15:06:33 UTC

Ah nice!

I did not get that from the flow you described.

Then - considering that it's in the docs - I'd say we can close this bug.

Closing according to comment 3 and comment 6.