Hi Andy, This is a known issue - after giving backends a chance to bring up network interfaces, netplan apply will iterate over interfaces that are still down, unbind them from their driver and rebind them. This can cause renaming of the interface.
In general, adding "set-name: ens7" to your YAML file should prevent it happening in the future. Note that netplan apply won't re-rename it if the interface is UP; netplan won't unplug the device unless you bring it down first. You can work around this by rebooting. (For this general issue I opened https://bugs.launchpad.net/netplan/+bug/1753868 - although it was one of the first netplan bugs I opened so it's a bit light on technical detail that I'd add if I were opening it now.) Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724895 Title: MTU not applied on private ethernet interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1724895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
