Bug 1346947 - initscripts should tell NetworkManger to ifcfg file even for NM_CONTROLLED=no
Summary: initscripts should tell NetworkManger to ifcfg file even for NM_CONTROLLED=no
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: initscripts
Version: 7.3
Hardware: x86_64
OS: Other
urgent
urgent
Target Milestone: rc
: ---
Assignee: initscripts Maintenance Team
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 1345919 1347958
Blocks: vdsm_config_NetworkMgr_to_be_passive 1351095
TreeView+ depends on / blocked
 
Reported: 2016-06-15 17:17 UTC by Marcel Kolaja
Modified: 2016-11-25 13:04 UTC (History)
16 users (show)

Fixed In Version: initscripts-9.49.30-1.el7_2.3
Doc Type: Bug Fix
Doc Text:
Cause: when a user edits an ifcfg-rh file to have NM_CONTROLLED=no, the expected behavior when calling ifup on the ifcfg-file is that NetworkManager stops managing the device. NetworkManager in default configuration does not automatically reload files from disk so a call to ifup must tell NetworkManager to reload the file. initscripts skipped reloading the file if it saw NM_CONTROLLED=no Consequence: after ifup of the file, NetworkManager would still manage the interface in parallel with initscripts. Fix: have initscripts always tell NetworkManager to reload the file. Result: a user can edit a file to have NM_CONTROLLED=no and on ifup, NetworkManager will stop managing the device.
Clone Of: 1345919
Environment:
Last Closed: 2016-08-02 18:25:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1523 0 normal SHIPPED_LIVE initscripts bug fix update 2016-08-02 22:20:22 UTC

Description Marcel Kolaja 2016-06-15 17:17:16 UTC
This bug has been copied from bug #1345919 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 5 Ying Cui 2016-07-25 10:26:58 UTC
Leos, could you help on this bug verification in you team? we - RHV must get this fix in one week, earlier is better. Thanks.

Comment 8 errata-xmlrpc 2016-08-02 18:25:11 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/RHBA-2016-1523.html


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