Unfortunately I cannot confirm it, because this provisioning is strictly dependent on the open-vm-tools which run early in the boot process.
The problem is that I have no access to the virtual machine until I manually connect the network interface, which in turn triggers the network configuration (which is done through ova/vapp, so through open- vm-tools, which passes the information to netplan, I guess) and cloud- init finally runs, meaning I can log in through the user configured in cloud-init. Which I cannot do beforehand cloud-init runs completely. Actually, the VM doesn't seem to boot fully until I connect the network card, that is to say, I don't get a login prompt. When I get the login prompt, everything works just fine. As I said, the practical consequence for me is only that the network interface isn't automatically getting connected to the VM. And the reason seems to be that open-vm-tools (i.e. toolsDeployPkg, the perl script which is part of open-vm-tools, as far as I understand) identify this netplan error and it exits unsuccessfully, which is turn means that the network interface remains disconnected. But otherwise, if the network card were to connect automatically, I mostly wouldn't care. Of course, that doesn't mean that there isn't an objective problem anyway. -- 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/cloud-images/+bug/2109487/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
