Hi, I haven't been to find this (NetworkManager) change documented. On: CentOS Linux release 7.1.1503 (Core) $ /bin/nmcli con NAME UUID TYPE DEVICE ens32 7629e52d-bd42-4cd5-a424-8c58e7e0bf37 802-3-ethernet ens32 On: CentOS Linux release 7.2.1511 (Core) $ /bin/nmcli con NAME UUID TYPE DEVICE System ens32 0c299aec-b628-4168-b3c7-5b00951f5eb8 802-3-ethernet ens32 The string "System " is part of the NAME. What might be my options to understand upstream's reasoning for this change and any possible workaround?
On 17 December 2015 at 06:06, Eugene Vilensky <evilensky at gmail.com> wrote:> Hi, > > I haven't been to find this (NetworkManager) change documented. > > On: > > CentOS Linux release 7.1.1503 (Core) > > $ /bin/nmcli con > NAME UUID TYPE DEVICE > ens32 7629e52d-bd42-4cd5-a424-8c58e7e0bf37 802-3-ethernet ens32 > > > On: > CentOS Linux release 7.2.1511 (Core) > > $ /bin/nmcli con > NAME UUID TYPE DEVICE > System ens32 0c299aec-b628-4168-b3c7-5b00951f5eb8 802-3-ethernet ens32 > > > The string "System " is part of the NAME. > > What might be my options to understand upstream's reasoning for this change > and any possible workaround? > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >I don't see 'System' in any of the CentOS 7.2.1511 boxes or VMs that were recently upgraded: /bin/nmcli con NAME UUID TYPE DEVICE virbr0 ccd9a252-0765-4e88-bb5d-bfc34eb278e3 bridge virbr0 enp5s0 ccbafeb6-ce6c-4713-b1ac-2cd0705bf16e 802-3-ethernet enp5s0 docker0 a4d7d1e6-0eb2-47d7-8c7e-b63cdc9d8f8d bridge docker0 virbr1-nic 9de87ba3-5c90-490a-b7f1-e273b0525fac generic virbr1-nic virbr1 0638f08b-b6c9-4e66-aee2-f64f2764ecf4 bridge virbr1 virbr0-nic b4b74c7e-1571-4a58-a1b4-0a72894e667a generic virbr0-nic cat /etc/centos-release CentOS Linux release 7.2.1511 (Core). -- Kind Regards Earl Ramirez
On Wed, Dec 16, 2015 at 4:47 PM, Earl A Ramirez <earlaramirez at gmail.com> wrote:> I don't see 'System' in any of the CentOS 7.2.1511 boxes or VMs that were > recently upgraded: >?Hi Earl, Have you tried a new install?? I agree, upgraded installations do not seem to be affected.