Bug 1309354 - NM does not match connection created from static iBFT configuration and connection created from iBFT (ip=ibft) in initramfs and creates redundant in-memory connection
NM does not match connection created from static iBFT configuration and conne...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda (Show other bugs)
7.2
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Radek Vykydal
Release Test Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-17 10:25 EST by Radek Vykydal
Modified: 2016-02-18 06:51 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-02-17 10:54:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Radek Vykydal 2016-02-17 10:25:27 EST
When network configuration is defined in iBFT table and ip=ibft boot option is supplied, the configuration is activated and corresponding ifcfg file is created in initramfs.

In case of static ip configuration NetworkManager does not match the connection and ifcfg file created in initramfs which results in creating of another persistent connection for the ifcfg file making Anaconda stumble upon it, eg displaying the connection in GUI for editing (although iBFT connections are read-only) and generating wrong dracut boot options for target system.
Comment 2 Radek Vykydal 2016-02-17 10:54:25 EST
Something different is actually happening here, I'll create a better report.

Note You need to log in before you can comment on or make changes to this bug.