Public bug reported: I will reference this comment here from the beginning:
https://github.com/vmware/open-vm- tools/issues/761#issuecomment-2834567855 I use packer to provision virtual machines starting from ubuntu cloud images (ova templates) on vSphere. When using cloud image release-20240710 (1.0-2ubuntu1.2), I don't have any issues with netplan and everything is provisioned correctly. When switching to the latest cloud image version release-20250403 (netplan 1.1.1-1~ubuntu24.04.1), "netplan apply" doesn't work correctly, ending up with the following error: "Failed to connect to system bus: No such file or directory and Falling back to a hard restart of systemd-networkd.service" This could be a regression caused by this backport https://bugs.launchpad.net/ubuntu/noble/+source/netplan.io/+bug/2077011, but I cannot be sure. In my case, the practical consequence is that the open-vm-tools scripts don't exit successfully and the network card is not automatically connected, as it should. This is somewhat less relevant for Canonical/netplan, but this is a scenario that a lot of people come across when dealing with provisioning Ubuntu virtual machines in vSphere using packer/terraform, so I'm just putting it out there. ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2109487 Title: netplan apply - cannot connect to system bus at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2109487/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
