Comment 5 for bug 1770082

On Wed, May 9, 2018 at 9:13 AM, Daniel Axtens
<email address hidden> wrote:
> Ryan: I removed /etc/netplan/50-cloud-init.yaml and rebooted repeatedly and
> I've never seen it regenerated.

Ah, right, it doesn't regenerate unless you change instance-ids.

>
> I also don't see anything in /run/netplan or /run/systemd/network that has
> been autogenerated.
>
> I haven't touched anything else generated by cloud-init. When would
> cloud-init regenerate a network config file?

Nothing, you're right. You can make a local change and reboot but typically
for cloud instances you'd want to have it set during the first boot.

So your scenario is:

1) deploy instance
2) log in and modify /etc/netplan/50-cloud-init.yaml to add a set-name:
3) reboot?

And the result is that you don't see a name change?

Yes, I think this is the udev scenario where it won't change a device
name whose 'name_assign_type' is either 3 or 4;

The driver unplug code in netplan is designed to workaround this
design issue with udev itself.

Can you confirm the driver for the interface you're renaming? ethtool
-i <iface name>

>
> --
> You received this bug notification because you are subscribed to
> netplan.
> Matching subscriptions: netplan
> https://bugs.launchpad.net/bugs/1770082
>
> Title:
> systemd-networkd not renaming devices on boot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions