On Fri, May 25, 2018 at 8:48 AM, Mathieu Trudel-Lapierre <[email protected]> wrote: > My recommended course of action for cosmic: > > - drop udevadm (net_setup_link) call from cloud-init
This will still be needed in the case that we have a network config with names. Cloud-init runs after udev coldplug, so any .link files would have to already be present. We're generating a network config post coldplug, but pre networking. Now, if after we netplan generate, if links could be applied or if networkd kicks udev to rename interfaces, that's fine. But it doesn't do that today. > - drop set-name "renaming" from cloud-init / maas I've already replied, but this is required for instances where udev doesn't run but network config has been provided. > - drop replug code in netplan; replace with proper .link code, possibly call to net_setup_link. +1 > - maybe write udev rule for renaming in netplan (think belt and suspenders) ? Instead of the .link files? > - make sure .link files are written correctly by netplan for renaming > - patch systemd to not second-guess renaming from .link files +1 > > -- > 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
