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 1394565 - on_boot for one of the nic is set to no for RHV-H ISO installation
Summary: on_boot for one of the nic is set to no for RHV-H ISO installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-13 16:18 UTC by RamaKasturi
Modified: 2016-11-16 15:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-16 15:06:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.