Back to bug 1369008

Who When What Removed Added
Michael Burman 2016-08-22 10:33:38 UTC CC danken
Dan Kenigsberg 2016-08-22 11:44:17 UTC Blocks 1368650
Rashid Khan 2016-08-22 12:17:11 UTC Priority unspecified high
Aniss Loughlam 2016-08-22 21:00:46 UTC CC aloughla
Thomas Haller 2016-08-23 11:12:16 UTC Assignee rkhan fgiudici
Rashid Khan 2016-09-01 20:37:53 UTC CC sukulkar
sushil kulkarni 2016-09-09 17:40:08 UTC Summary [nmtui] - When creating a bond via nmtui it creates ifcfg files with MASTER=UUID instead of MASTER=device_name [RFE] [nmtui] - When creating a bond via nmtui it creates ifcfg files with MASTER=UUID instead of MASTER=device_name
RHEL Program Management 2016-09-09 19:31:51 UTC Keywords FutureFeature
Vladimir Benes 2016-11-08 08:14:06 UTC CC vbenes
Lubomir Rintel 2016-11-11 17:36:42 UTC Assignee fgiudici lrintel
Thomas Haller 2016-12-01 17:31:13 UTC Status NEW POST
Blocks 1225471
Lubomir Rintel 2016-12-05 12:41:53 UTC CC lkundrak
sushil kulkarni 2016-12-08 21:42:32 UTC Blocks 1393481
Thomas Haller 2016-12-15 18:08:27 UTC Status POST MODIFIED
Blocks 1225471
Yaniv Lavi 2017-01-05 12:49:13 UTC Keywords FutureFeature
CC ydary
Summary [RFE] [nmtui] - When creating a bond via nmtui it creates ifcfg files with MASTER=UUID instead of MASTER=device_name Once NetworkManager is stopped, the ifcfg files it created via nmtui\cockpit are incompatible with initscripts, since MASTER=UUID instead of MASTER=device_name
Siddharth Nagar 2017-01-09 15:36:37 UTC CC mburman
Flags needinfo?(mburman)
Dan Kenigsberg 2017-01-09 15:57:22 UTC Flags needinfo?(mburman)
Jaroslav Reznik 2017-01-13 13:18:14 UTC Blocks 1413048
Jaroslav Reznik 2017-01-13 13:19:13 UTC Keywords ZStream
Gil Klein 2017-02-02 13:58:43 UTC CC gklein
Severity medium high
errata-xmlrpc 2017-02-10 16:33:15 UTC Status MODIFIED ON_QA
Lubomir Rintel 2017-02-20 19:00:27 UTC Blocks 1225471
cshao 2017-02-21 07:01:06 UTC CC cshao
Lubomir Rintel 2017-02-21 08:30:01 UTC Doc Text * Previously, when creating a Team, Bridge or Bond slave NetworkManager would default to writing the connection UUID of the master connection to the ifcfg file. This is incompatible with the legacy network service that only supports using the device interface name. With this update, NetworkManager attempts to write a device name in addition to the connection UUID for improved compatibility with the legacy network service. BZ#1369008)

Note that UUID alone will be used in case NetworkManager is not able to resolve the master connection into a device name. That is currently the case when the slave connections are added before the master connection is saved in nmtui.
Doc Type If docs needed, set a value Enhancement
Francesco Giudici 2017-02-21 17:33:30 UTC CC fgiudici
Mirek Jahoda 2017-02-24 15:54:41 UTC CC mjahoda
Doc Text * Previously, when creating a Team, Bridge or Bond slave NetworkManager would default to writing the connection UUID of the master connection to the ifcfg file. This is incompatible with the legacy network service that only supports using the device interface name. With this update, NetworkManager attempts to write a device name in addition to the connection UUID for improved compatibility with the legacy network service. BZ#1369008)

Note that UUID alone will be used in case NetworkManager is not able to resolve the master connection into a device name. That is currently the case when the slave connections are added before the master connection is saved in nmtui.
Previously, when creating a Team, Bridge, or Bond slave, NetworkManager wrote the connection UUID of the master connection to the ifcfg file. This was not compatible with the legacy network service that supports only using the device interface name. With this update, NetworkManager attempts to write a device name in addition to the connection UUID and compatibility with the legacy network service is now improved.

Note that only UUID is used in case NetworkManager is not able to resolve the master connection into a device name. That is currently the case when the slave connections are added before the master connection is saved in the nmtui tool.
Mirek Jahoda 2017-02-27 09:55:34 UTC Docs Contact mjahoda
Doc Text Previously, when creating a Team, Bridge, or Bond slave, NetworkManager wrote the connection UUID of the master connection to the ifcfg file. This was not compatible with the legacy network service that supports only using the device interface name. With this update, NetworkManager attempts to write a device name in addition to the connection UUID and compatibility with the legacy network service is now improved.

Note that only UUID is used in case NetworkManager is not able to resolve the master connection into a device name. That is currently the case when the slave connections are added before the master connection is saved in the nmtui tool.
Previously, when creating a Team, Bridge, or Bond slave, NetworkManager wrote the Universally Unique Identifier (UUID) of the master connection to the ifcfg file. This was not compatible with the legacy network service that supports only using the device interface name. With this update, NetworkManager attempts to write a device name in addition to the connection UUID and compatibility with the legacy network service is now improved.

Note that only UUID is used in case NetworkManager is not able to resolve the master connection into a device name. That is currently the case when the slave connections are added before the master connection is saved in the nmtui tool.
Mirek Jahoda 2017-02-28 09:41:01 UTC Doc Text Previously, when creating a Team, Bridge, or Bond slave, NetworkManager wrote the Universally Unique Identifier (UUID) of the master connection to the ifcfg file. This was not compatible with the legacy network service that supports only using the device interface name. With this update, NetworkManager attempts to write a device name in addition to the connection UUID and compatibility with the legacy network service is now improved.

Note that only UUID is used in case NetworkManager is not able to resolve the master connection into a device name. That is currently the case when the slave connections are added before the master connection is saved in the nmtui tool.
Previously, when creating a Team, Bridge, or Bond slave, NetworkManager wrote the Universally Unique Identifier (UUID) of the master connection to the ifcfg file. This was not compatible with the legacy network service that supports only using the device interface name. With this update, NetworkManager attempts to write a device name in addition to the connection UUID, and compatibility with the legacy network service has been improved.

Note that only UUID is used in case NetworkManager is not able to resolve the master connection into a device name. That is currently the case when slave connections are added before the master connection is saved in the nmtui tool.
Thomas Haller 2017-04-13 13:36:16 UTC Blocks 1225471
Lubomir Rintel 2017-04-25 17:47:54 UTC Fixed In Version NetworkManager-1.8.0-0.2.git20170215.1d40c5f4.el7
Vladimir Benes 2017-05-12 12:21:37 UTC Status ON_QA VERIFIED
errata-xmlrpc 2017-08-01 09:17:07 UTC Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2017-08-01 05:17:07 UTC
Gil Klein 2019-04-28 13:11:55 UTC CC gklein

Back to bug 1369008