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
Summary: NM does not match connection created from static iBFT configuration and conne...
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
unspecified
Target Milestone: rc
: ---
Assignee: Radek Vykydal
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-17 15:25 UTC by Radek Vykydal
Modified: 2016-02-18 11:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-17 15:54:25 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Radek Vykydal 2016-02-17 15:25:27 UTC 
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 15:54:25 UTC 
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.