Bug 1346947
| Summary: | initscripts should tell NetworkManger to ifcfg file even for NM_CONTROLLED=no | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | initscripts | Assignee: | initscripts Maintenance Team <initscripts-maint-list> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.3 | CC: | atragler, bgalvani, bmcclain, danken, desktop-qa-list, fdeutsch, jscotka, lpol, lrintel, mburman, mkalinin, mkolaja, ovasik, rkhan, thaller, ycui |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1345919 | Environment: | |
| Last Closed: | 2016-08-02 18:25:11 UTC | Type: | --- |
| 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: | 1345919, 1347958 | ||
| Bug Blocks: | 1326798, 1351095 | ||
|
Description
Marcel Kolaja
2016-06-15 17:17:16 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. Verified by testcase: https://beaker.engineering.redhat.com/matrix/?toggle_nacks_on=on&job_ids=1416277+1416279 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 |