Comment 4 for bug 1919177

Hi,

I think the complete suite of events is well shown here:

Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: enP28243s1np0: Interface name change detected, enP28243s1np0 has been renamed to eth1.
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: eth1: Interface name change detected, eth1 has been renamed to enP28243s1np0.
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: enP28243s1np0: Link UP
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: eth0: Link UP
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: eth0: Gained carrier
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: enP28243s1np0: Gained carrier
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: enP28243s1np0: Link DOWN
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: enP28243s1np0: Lost carrier
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: eth0: Link DOWN
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: eth0: Lost carrier
Apr 12 08:25:00 hirsute-acc systemd[1]: Finished Wait for Network to be Configured.
Apr 12 08:25:00 hirsute-acc systemd[1]: Starting Initial cloud-init job (metadata service crawler)...
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: enP28243s1np0: Link UP
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: eth0: Link UP
Apr 12 08:25:00 hirsute-acc systemd-networkd[652]: eth0: Gained carrier
Apr 12 08:25:00 hirsute-acc cloud-init[662]: 2021-04-12 08:25:00,954 - azure.py[ERROR]: Failed to read /var/lib/dhcp/dhclient.eth0.leases: [Errno 2] No such file or directory: '/var/lib/dhcp/d
hclient.eth0.leases'

The link goes down, then systemd stops waiting for the network configuration, then cloud-init starts, shortly after the link goes UP again but cloud-init fails (shows an error related to dhcp lease).