Testing cloud-init-0.7.8 for Leap-42.1 there is a systemd message in the
journal:
---cut here---
Sep 20 15:37:21 vm3 systemd[1]: Breaking ordering cycle by deleting job
cloud-init.target/start
Sep 20 15:37:21 vm3 systemd[1]: Job cloud-init.target/start deleted to break
ordering cycle starting with multi-user.target/start
Sep 20 15:37:21 vm3 systemd[1]: Cannot find unit for notify message of PID 83.
Sep 20 15:37:21 vm3 systemd[1]: Found ordering cycle on multi-user.target/start
Sep 20 15:37:21 vm3 systemd[1]: Found dependency on
systemd-logind.service/start
Sep 20 15:37:21 vm3 systemd[1]: Found dependency on cloud-final.service/start
Sep 20 15:37:21 vm3 systemd[1]: Found dependency on multi-user.target/start
Sep 20 15:37:21 vm3 systemd[1]: Breaking ordering cycle by deleting job
systemd-logind.service/start
Sep 20 15:37:21 vm3 systemd[1]: Job systemd-logind.service/start deleted to
break ordering cycle starting with multi-user.target/start
Sep 20 15:37:21 vm3 systemd[1]: Found ordering cycle on multi-user.target/start
Sep 20 15:37:21 vm3 systemd[1]: Found dependency on cloud-init.target/start
Sep 20 15:37:21 vm3 systemd[1]: Found dependency on cloud-final.service/start
Sep 20 15:37:21 vm3 systemd[1]: Found dependency on multi-user.target/start
---cut here---
Listing the dependencies with systemctl (thinned output for readability):
---cut here---
leap-ci:~ # systemctl --no-pager show -p After -p Before cloud-init.target
Before=multi-user.target
After=cloud-config.service cloud-final.service cloud-init.service
leap-ci:~ # systemctl --no-pager show -p After -p Before multi-user.target
Before=graphical.target cloud-final.service
After=basic.target systemd-logind.service after-local.service
cloud-init.service wicked.service cloud-config.service cloud-init.target
---cut here---
IIUC, cloud-final.service is supposed to run before cloud-init.target, followed
by multi-user.target. But multi-user.target also is supposed to run before
cloud-final.service, which is impossible.
I didn't check the other dependencies in detail.