I've just tested, and this doesn't seem to reproduce when launching from a captured image (with 90-hotplug-azure.yaml restored and `cloud-init clean` executed). So I think I've exhausted the ways in which I can attempt to gain more insight into what's happening during the part of boot where this reproduces.
I think we're going to need an image published with some debugging built into it (which, hopefully, will continue to reproduce the issue). If https://paste.ubuntu.com/p/qkwmDvRRrB/ is installed and enabled, we should get a whole bunch of udev information, which may shed some light onto what's going on from an ordering POV.
I'm not sure if there's any more networking/networkd-specific debugging we should also add.
I've just tested, and this doesn't seem to reproduce when launching from a captured image (with 90-hotplug- azure.yaml restored and `cloud-init clean` executed). So I think I've exhausted the ways in which I can attempt to gain more insight into what's happening during the part of boot where this reproduces.
I think we're going to need an image published with some debugging built into it (which, hopefully, will continue to reproduce the issue). If https:/ /paste. ubuntu. com/p/qkwmDvRRr B/ is installed and enabled, we should get a whole bunch of udev information, which may shed some light onto what's going on from an ordering POV.
I'm not sure if there's any more networking/ networkd- specific debugging we should also add.