> Separately we really ought to port networkd from dbus communication to
varlink such that it can be used safely on critical boot path. The rest
of the Systemd critical components are already using varlink.
+1
> did you mean to mark Ubuntu(Systemd) as affected?
Yes, I'll update that thanks.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1997124
Title:
Netplan/Systemd/Cloud-init/Dbus Race
Status in cloud-init:
New
Status in systemd package in Ubuntu:
New
Bug description:
Cloud-init is seeing intermittent failures while running `netplan
apply`, which appears to be caused by a missing resource at the time
of call.
The symptom in cloud-init logs looks like:
Running ['netplan', 'apply'] resulted in stderr output: Failed to
connect system bus: No such file or directory
I think that this error[1] is likely caused by cloud-init running
netplan apply too early in boot process (before dbus is active).
Today I stumbled upon this error which was hit in MAAS[2]. We have
also hit it intermittently during tests (we didn't have a reproducer).
Realizing that this may not be a cloud-init error, but possibly a
dependency bug between dbus/systemd we decided to file this bug for
broader visibility to other projects.
I will follow up this initial report with some comments from our
discussion earlier.
[1] https://github.com/canonical/netplan/blob/main/src/dbus.c#L801
[2]
https://discourse.maas.io/t/latest-ubuntu-20-04-image-causing-netplan-error/5970
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1997124/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
