Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1432886

Summary: network tui: changing ipv4 configuration from static to dhcp doesn't work
Product: Red Hat Enterprise Linux 7 Reporter: Radek Vykydal <rvykydal>
Component: anacondaAssignee: Radek Vykydal <rvykydal>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: jstodola, pkotvan, sbueno
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-21.48.22.103-1 Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 08:55:41 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 Radek Vykydal 2017-03-16 10:22:19 UTC
Description of problem:

When changing NIC configuration from initramfs in tui is broken.

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

RHEL-7.4-20170315.n.1

How reproducible:

Always

A) dhcp (initramfs) -> static (tui)

Steps to Reproduce:

1. Run text network installation with one NIC, activated with dhcp in initramfs (no boot option or ip=ens3:dhcp)
2. In tui change the configuration to static with applying it in installer environment (check 8) [x] Apply configuration in installer)

Actual results:
The configuration is not applied, there is BOOTPROTO=none in the ifcfg file

Expected results:
The static configuration is applied in installer, ifcfg file is fine.

This is a regression from RHEL 7.3 (might be related to the new NM 1.8 in 7.4)

B) static (initramfs) -> dhcp (tui)

Steps to Reproduce:

1. Run text network installation with one NIC, activated with static configuration in initramfs (eg ip=10.34.102.233::10.34.102.254:255.255.255.0::ens3:none nameserver=10.34.39.2
2. In tui change the configuration to dhcp with applying it in installer environment (check 8) [x] Apply configuration in installer)
   - It is not possible to remove the nameserver, gateway and netmask options.

Actual results:
NIC gets dhcp address but also keeps static configuration (ifcfg file contains BOOTPROTO=dhcp and IPADDR, PREFIX, GATEWAY, DNS1 set)

Expected results:
NIC is recofigured with dhcp ip address, ifcfg file is fine (contains only BOOTPROTO=dhcp, no IPADDR, no PREFIX, no GATEWAY) 
Also it should be possible to clear nameserver, gateway and netmask settings in tui.

This is the same in RHEL 7.3.

Comment 2 Radek Vykydal 2017-03-16 10:24:47 UTC
We should assess severity of the BZ also in the light of tui network spoke being added to initial setup in RHEL 7.4.

Comment 4 Radek Vykydal 2017-03-16 12:14:38 UTC
(In reply to Radek Vykydal from comment #0)


> Actual results:
> The configuration is not applied, there is BOOTPROTO=none in the ifcfg file

The none value is ok.

Comment 5 Radek Vykydal 2017-03-16 13:00:02 UTC
I am not able to reproduce A), maybe I actually forgot to check the 8) [x] to activate the connection.
Removing Regression keyword and keeping the BZ for the issue B).

Comment 6 Radek Vykydal 2017-03-17 10:58:51 UTC
https://github.com/rhinstaller/anaconda/pull/997

Comment 8 Radek Vykydal 2017-03-21 10:30:30 UTC
PR for kickstart test: https://github.com/rhinstaller/kickstart-tests/pull/80/

Comment 9 Fedora Update System 2017-04-28 13:28:48 UTC
anaconda-26.21.4-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f620d8c7c2

Comment 10 Fedora Update System 2017-04-30 03:52:15 UTC
anaconda-26.21.4-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-f620d8c7c2

Comment 11 Peter Kotvan 2017-05-11 08:41:37 UTC
Reproduced with anaconda-21.48.22.93-1, verified on RHEL-7.4-20170504.0 with anaconda-21.48.22.111-1.el7.x86_64.rpm. Thanks.

Comment 12 errata-xmlrpc 2017-08-01 08:55:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2293