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.)
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 /bugs.launchpad .net/netplan/ +bug/1753868 - although it was one of
https:/
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