Back to bug 1374837
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Lukáš Nykrýn | 2016-09-12 07:54:46 UTC | Status | NEW | ASSIGNED |
| David Kaspar // Dee'Kej | 2016-10-25 14:28:35 UTC | Blocks | 1380361 | |
| Assignee | initscripts-maint-list | dkaspar | ||
| David Kaspar // Dee'Kej | 2016-10-25 14:34:41 UTC | Keywords | Patch | |
| David Kaspar // Dee'Kej | 2016-11-25 13:04:40 UTC | CC | initscripts-maint-list | |
| Jan Ščotka | 2016-11-30 13:28:35 UTC | CC | jscotka | |
| Branislav Blaškovič | 2017-02-20 14:56:40 UTC | CC | bblaskov | |
| David Kaspar // Dee'Kej | 2017-03-22 17:50:37 UTC | Status | ASSIGNED | MODIFIED |
| Depends On | 1392766 | |||
| errata-xmlrpc | 2017-03-30 15:30:16 UTC | Status | MODIFIED | ON_QA |
| David Kaspar // Dee'Kej | 2017-04-03 08:55:16 UTC | Fixed In Version | initscripts-9.49.38-1.el7 | |
| Leos Pol | 2017-04-26 10:55:56 UTC | Status | ON_QA | VERIFIED |
| QA Contact | qe-baseos-daemons | lpol | ||
| David Kaspar // Dee'Kej | 2017-05-10 12:00:12 UTC | Doc Text | Setting NM_CONTROLLED directive now works correctly across all ifcfg-* files. In previous versions of Red Hat Enterprise Linux 7 setting NM_CONTROLLED=no in one of the ifcfg-* file could result in other interfaces inheriting this configuration, thus marking them to not be controlled via NetworkManager. | |
| Doc Type | If docs needed, set a value | Release Note | ||
| Lenka Špačková | 2017-05-11 11:34:48 UTC | Docs Contact | fhanzelk | |
| Filip Hanzelka | 2017-05-23 16:57:55 UTC | Doc Text | Setting NM_CONTROLLED directive now works correctly across all ifcfg-* files. In previous versions of Red Hat Enterprise Linux 7 setting NM_CONTROLLED=no in one of the ifcfg-* file could result in other interfaces inheriting this configuration, thus marking them to not be controlled via NetworkManager. | Setting "NM_CONTROLLED" now works correctly across all the `ifcfg-*` files In previous versions of Red Hat Enterprise Linux 7, setting the "NM_CONTROLLED=no" parameter in one of the `ifcfg-*` files sometimes resulted in other interfaces inheriting this configuration. This prevented *NetworkManager* from controlling these interfaces. The issue has now been resolved, and setting the "NM_CONTROLLED" directive now works correctly across all the `ifcfg-*` files. As a result, the user can choose which interface is controlled by *NetworkManager*, and which is not. |
| Filip Hanzelka | 2017-05-25 09:19:53 UTC | Doc Text | Setting "NM_CONTROLLED" now works correctly across all the `ifcfg-*` files In previous versions of Red Hat Enterprise Linux 7, setting the "NM_CONTROLLED=no" parameter in one of the `ifcfg-*` files sometimes resulted in other interfaces inheriting this configuration. This prevented *NetworkManager* from controlling these interfaces. The issue has now been resolved, and setting the "NM_CONTROLLED" directive now works correctly across all the `ifcfg-*` files. As a result, the user can choose which interface is controlled by *NetworkManager*, and which is not. | Setting "NM_CONTROLLED" now works correctly across all the `ifcfg-*` files When the "NM_CONTROLLED=no" parameter was set for an interface in its `ifcfg-*` file, other interfaces in some cases inherited this configuration. This behaviour prevented the *NetworkManager* daemon from controlling these interfaces. The issue has now been resolved, and setting the "NM_CONTROLLED" parameter now works correctly across all the `ifcfg-*` files. As a result, the user can choose which interface is controlled by *NetworkManager*, and which is not. |
| errata-xmlrpc | 2017-08-01 04:02:03 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2017-08-01 07:29:01 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-08-01 03:29:01 UTC | |||
| Pasi Karkkainen | 2017-08-02 07:37:20 UTC | CC | pasik |
Back to bug 1374837