upgrade to 1068.8.0 changes network interface name

[Umesh Tyagi]

All our CoreOS machines which had static IP configuration in place are booting as DHCP after upgrading to 1068.8.0. This is because the upgrade is causing the network device name to change throwing off the "[Match]" section in static IP configuration file.  

Our CoreOS VMs running 1010.5.0 had network interfaces named as 'eno16780032' but upgrade to 1068.8.0 renamed it to 'ens192'

Is there a way to enforce the name of interface names so it doesn't change on us with newer OS updates  ?

thanks.

[Michael Marineau]

Sounds like udev started discarding interface numbers from the firmware above a certain value as invalid. Considering that I doubt there are 16780032 onboard interfaces this sounds like a reasonable bug fix but an unfortunate change to find by surprise. Generally we avoid allowing such changes through when they are arbitrary default changes (upstream has changed how virtio devices are named a couple times now) so I think you should be safe with the new names. As an added protection you can copy 99-default.link to a new lower numbered file in /etc/systemd/network and remove onboard from the list to prevent the weird high-numbered names from reappearing. It will also work on older versions if you need to boot a system with an old version but want it to stick to the new name. The new name is derived from the PCI slot instead of firmware data which should be stable.

--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Seán C. McCord]

Also, though, it's safer to just not ever match on the interface name.  That's why systemd-networkd allows you to match on other things, like the MAC address.

--

Seán C McCord

CyCore Systems, Inc

+1 888 240 0308

PGP/GPG: http://cycoresys.com/scm.asc