Comment 15 for bug 1669564

On Tue, May 2, 2017 at 3:05 AM, Dimitri John Ledkov <email address hidden>
wrote:

> Looking at the journal files from the netplan-udev that fail, I see that
> links are already renamed, before cloud-init renders things:
>
> Mar 09 17:51:12 ubuntu kernel: virtio_net virtio0 ens3: renamed from eth0
> Mar 09 17:51:12 ubuntu kernel: virtio_net virtio1 ens4: renamed from eth1
> Mar 09 17:51:14 ubuntu kernel: virtio_net virtio0 interface0: renamed from
> ens3
> Mar 09 17:51:14 ubuntu kernel: virtio_net virtio1 interface1: renamed from
> ens4
> Mar 09 17:51:15 ubuntu cloud-init[382]: WARK: ['netplan', 'generate']:
> stdout:
> Mar 09 17:51:15 ubuntu cloud-init[382]: WARK: ['udevadm', 'trigger',
> '--verbose', '--subsystem-match=net', '--action=add']: stdout:
>

> This seems to me as a test case that did not fail, or there are stray
> files left during this test run.
>

The renames are not the issue; it's the .link files which set things like
MTU.

cloud-init may issue ip set dev link name commands to apply a new name, if
it's not already set but won't
issue them if the names are what it expects.

>
> A full sosreport might be helpful, maybe there are persistent-net rules
> written out, in addition to link files?
>

I can collect a sosreport; I don't think it provides anything additional,
the core issue
is inside systemd itself w.r.t how the udev code is invoked by
systemd-udevd