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 1444887

Summary: Wrong connection edited in UI when a device activated in initramfs (boot options) is reconfigured by kickstart without reactivation
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: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: bugproxy, hannsj_uhl, jstodola, mkolman, pjanda, pkotvan, sbueno
Target Milestone: rc   
Target Release: 7.4   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-21.48.22.113-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:
Bug Depends On:    
Bug Blocks: 1299988    

Description Radek Vykydal 2017-04-24 13:36:19 UTC 
Description of problem:

If a device activated in initramfs is reconfigured via kickstart without being activated in installer (based on network --activate / --on-activate options), the connection exposed in GUI is not the one corresponding to persistent (ifcfg / target system) configuration but a connection created for initramfs device config.
If it is changed in UI, it is saved as another persistent configuration ifcfg-<NIC>-1, eg ifcfg-ens3-1.

Version-Release number of selected component (if applicable):
RHEL 7.3 GA
RHEL-7.4-20170421.n.1

How reproducible:

Alway, but depends on order of connections for a device returned by NM which is may not be determininstic.


Steps to Reproduce:

1. Run installation requiring network in initramfs (eg pxe installation) with ip=ens3:dhcp (or no ip= specified which defaults to dhcp)

Kickstart file contains reconfiguration of the device without activation in installer:

network --device=ens3 --bootproto=static --ip=10.34.102.233 --gateway=10.34.102.254 --netmask=255.255.255.0 --activate --nameserver=10.34.39.2 --no-activate


2a. GUI: Edit ens3 device ipv4 network configuration in network spoke - dhcp is preset (because we are not editing the ifcfg connection, but in-memory NM connection).

2b. TUI: Edit ens3 connection, values for the ifcfg connection (static ipv4 config) are displayed.

3. Modify and save the configuration.

Actual results:

For both GUI and TUI, additional ifcfg-ens3-1 ifcfg file is created for the configuration modified in UI, instead of changing ifcfg-ens3 which is keeping the kickstart configuration.

Expected results:

In GUI, ifcfg connection is displayed.
Both in GUI and TUI, the persistent connetion (ifcfg-ens3) is updated with values configured from UI.

Additional info:

A kickstart test failing due to the same root cause:
https://github.com/rhinstaller/kickstart-tests/blob/master/network-noipv4-httpks.ks.in
Comment 2 Radek Vykydal 2017-04-25 11:04:04 UTC 
https://github.com/rhinstaller/anaconda/pull/1038
Comment 4 Petr Janda 2017-04-28 06:53:47 UTC 
accidentally removed qa_ack+ setting it back
Comment 6 Fedora Update System 2017-06-13 16:25:06 UTC 
anaconda-26.21.8-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f8d6a1f05a
Comment 8 Fedora Update System 2017-06-15 13:57:42 UTC 
anaconda-26.21.8-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-f8d6a1f05a
Comment 10 Fedora Update System 2017-06-16 12:16:57 UTC 
anaconda-26.21.9-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f8d6a1f05a
Comment 11 Fedora Update System 2017-06-16 22:22:52 UTC 
anaconda-26.21.9-1.fc26, pykickstart-2.35-1.fc26, python-blivet-2.1.9-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-f8d6a1f05a
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
Comment 13 Red Hat Bugzilla 2023-09-14 03:56:54 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days