While running the test plan, I discovered an issue with the way the
systemd service is configured. The service file configures
Before=network-pre.target but doesn't set DefaultDependencies=no. On
Noble and Jammy, this causes a dependency cycle to occur:

Sep 03 16:27:16 ubuntu systemd[1]: sysinit.target: Found ordering cycle on 
cloud-init.service/start
Sep 03 16:27:16 ubuntu systemd[1]: sysinit.target: Found dependency on 
systemd-networkd-wait-online.service/start
Sep 03 16:27:16 ubuntu systemd[1]: sysinit.target: Found dependency on 
systemd-networkd.service/start
Sep 03 16:27:16 ubuntu systemd[1]: sysinit.target: Found dependency on 
network-pre.target/start
Sep 03 16:27:16 ubuntu systemd[1]: sysinit.target: Found dependency on 
azure-proxy-agent.service/start
Sep 03 16:27:16 ubuntu systemd[1]: sysinit.target: Found dependency on 
basic.target/start
Sep 03 16:27:16 ubuntu systemd[1]: sysinit.target: Found dependency on 
sysinit.target/start
Sep 03 16:27:16 ubuntu systemd[1]: sysinit.target: Job cloud-init.service/start 
deleted to break ordering cycle starting with sysinit.target/start

From 25.04, cloud-init doesn't depends anymore on systemd-networkd-wait-
online.service which mitigate the issue. However, I think similar cycle
could still happen with other services.

The cycle involving cloud-init on 22.04 and 24.04 completely breaks the
image if the agent is pre-installed as it prevents cloud-init from
running.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2115197

Title:
  [SRU] Backport azure-proxy-agent 1.0.30-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/azure-proxy-agent/+bug/2115197/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to