Comment 3 for bug 1919177

Hi Paride,

Thanks for checking the logs. I can confirm that the network seems correctly configured when I access the VM.
As far as I can see with journalctl, the mellanox's network interface is not fully configured when the cloud-init "init" steps startup.

Good instance (no issue):

Mar 22 14:25:40 hirsute-acc systemd-networkd[666]: eth0: DHCPv4 address 10.0.0.4/24 via 10.0.0.1
Mar 22 14:25:41 hirsute-acc cloud-init[678]: Cloud-init v. 21.1-19-gbad84ad4-0ubuntu1 running 'init' at Mon, 22 Mar 2021 14:25:41 +0000. Up 3970.29 seconds.

Bad instance (with issue):

Mar 22 16:26:44 hirsute-acc-2 cloud-init[662]: Cloud-init v. 21.1-19-gbad84ad4-0ubuntu1 running 'init' at Mon, 22 Mar 2021 16:26:44 +0000. Up 14.23 seconds.
Mar 22 16:26:48 hirsute-acc-2 systemd-networkd[653]: eth0: DHCPv4 address 10.0.0.4/24 via 10.0.0.1

It's weird because in both cases, I can this line before cloud-init starts up:

Mar 22 16:26:44 hirsute-acc-2 systemd[1]: Finished Wait for Network to be Configured.

which is expected since cloud-init unit is set to run after "systemd-networkd-wait-online.service".

So I am trying to understand why "systemd-networkd-wait-online" reports that the interfaces are configured when apparently they are not.