Bug 1273323

Summary: Don't set NM_CONTROLLED=no for devices used for root on iSCSI
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.2CC: jstodola, mkovarik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-21.48.22.60-1 Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
: 1387678 (view as bug list) Environment:
Last Closed: 2016-11-03 23:18:35 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: 1387678    

Description Radek Vykydal 2015-10-20 08:34:22 UTC
This paragraph from RHEL 7 Installation Guide

"If / is placed on an iSCSI target, Anaconda sets NetworkManager to ignore any network interfaces that were active during the installation process. These interfaces will also be configured by initrd when the system starts. If NetworkManager were to reconfigure these interfaces, the system would lose its connection to /."

is no longer true. NM should handle connection established in initramfs just fine.
Port
https://github.com/rhinstaller/anaconda/commit/9af79b2fca8783face495f88c6c4b13001f6c9f1
from master (+ remove no longer used import).

Comment 2 Michal Kovarik 2016-07-27 10:43:13 UTC
Verified on RHEL-7.3-20160719.1 with anaconda-21.48.22.80-1. NM_CONTROLLED is not set in ifcfg script, when root is on iscsi device.

Comment 4 errata-xmlrpc 2016-11-03 23:18:35 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://rhn.redhat.com/errata/RHEA-2016-2158.html