Bug 1036847

Summary: Update ifup/ifdown NetworkManager interaction
Product: Red Hat Enterprise Linux 7 Reporter: Dan Winship <danw>
Component: initscriptsAssignee: initscripts Maintenance Team <initscripts-maint-list>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Ščotka <jscotka>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: jscotka, lnykryn
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: initscripts-9.49.13-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1036701 Environment:
Last Closed: 2014-06-13 09:48:36 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:
Bug Depends On:    
Bug Blocks: 1022256    

Description Dan Winship 2013-12-02 18:21:06 UTC 
+++ This bug was initially created as a clone of Bug #1036701 +++

ifup and ifdown have one problem that's new in F20 and another that has always existed but might be more commonly seen in F20:

1. In its default configuration in F20, NetworkManager no longer automatically reloads ifcfg files when they change, so we need to reload them manually, so that, eg, creating/editing an ifcfg file and then using "ifup" on it has the expected behavior.

2. Just because an ifcfg file has a UUID= line doesn't mean that it's managed by NM. (In particular, if someone changes their default Ethernet connection from "TYPE=Ethernet" to "TYPE=OVSPort", but doesn't remove the UUID line, then ifup will currently hand it off to NM, but NM won't know what to do with it. Instead, ifup should be handling it itself.)

---


The patch is the same as in 1036701. The required NM version in RHEL 7 is 
0.9.9.0-26.git20131108
Comment 4 Ludek Smid 2014-06-13 09:48:36 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.