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 1391852 - Network configure can't be saved during Anaconda interactive installation
Summary: Network configure can't be saved during Anaconda interactive installation
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: pre-dev-freeze
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: ovirt-node-ng-platform
TreeView+ depends on / blocked
 
Reported: 2016-11-04 09:05 UTC by cshao
Modified: 2016-11-18 11:10 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-18 11:10:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
disable-nic (87.66 KB, image/png)
2016-11-04 09:05 UTC, cshao 		no flags Details
/var/log; /tmp; sosreport (8.17 MB, application/x-gzip)
2016-11-04 09:11 UTC, cshao 		no flags Details
View All

Description cshao 2016-11-04 09:05:14 UTC 
Created attachment 1217328 [details]
disable-nic

Description of problem:
  During anaconda interactive installation RHVH via pxe, all the nics will
be enabled by default. We only keep one nic enable status and disable
all the remaining nics.

  Try to finish the installation with correct steps. Login RHVH, check NICs status.

  The disabled nic should not be up and can not show the ip address anymore.


Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.0-20161027.1
imgbased-0.8.6-0.1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Anaconda interactive installation RHVHvia pxe.
2. Only keep one nic enable status and disable all the remaining nics.
3. Try to finish the installation with correct steps.
4. Login RHVH, check nic status


Actual results:
The disabled nic is still up and can get ip address

Expected results:
The disabled nic should not be up and can not show the ip address anymore.

Additional info:
Comment 1 cshao 2016-11-04 09:11:42 UTC 
Created attachment 1217329 [details]
/var/log; /tmp; sosreport
Comment 3 Radek Vykydal 2016-11-18 11:10:03 UTC 
Both ens3 and ens4 devices were activated in initramfs stage because no particular device was specified via installer boot options (eg by ip=ens3:dhcp [1]) and in this case dracut tries to activate all devices with dhcp. All devices activated in initramfs stage have ONBOOT=yes (activate automatically on boot) set unless overridden by kickstart configuration or changed in GUI. What you are hitting is that just switching the device OFF on GUI doesn't change its ONBOOT property, it needs to be configured in GUI similarly as described in https://bugzilla.redhat.com/show_bug.cgi?id=1394565#c3, ie "Configure" -> "General" tab -> uncheck "Automatically connect..."

So to have ONBOOT=no configured for ens4 on installed system you'd need either:

- not activate ens4 in initramfs/dracut which would be achieved by specifying only ens3 to be activated (eg ip=ens3:dhcp) [1]

- or override ens4 configuration in kickstart with onboot=no, eg
network --device=ens4 --onboot=no
(--bootproto=dhcp is default)

- or change the ens4 ONBOOT value in GUI as hinted above.

[1] specifying the device to be activated in initramfs via BOOTIF added by pxelinux to boot options would work too. You'd need to add
ipappend 2
to your pxelinux config so it supplies the BOOTIF value. Dracut should activate only the PXE booting device then (regardless of ksdevice=bootif value being among boot options or not, it is deprecated and no more required in 7.3 IIRC)
Note You need to log in before you can comment on or make changes to this bug.