break ordering cycle starting with sysinit.target/start

Bug #1995803 reported by Carlos F.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Expired
Undecided
Unassigned

Bug Description

Dmesg reports:

[ 3.665652] systemd[1]: sysinit.target: Found ordering cycle on cloud-init.service/start
[ 3.667504] systemd[1]: sysinit.target: Found dependency on systemd-networkd-wait-online.service/start
[ 3.669684] systemd[1]: sysinit.target: Found dependency on systemd-networkd.service/start
[ 3.671600] systemd[1]: sysinit.target: Found dependency on network-pre.target/start
[ 3.673488] systemd[1]: sysinit.target: Found dependency on ufw.service/start
[ 3.675267] systemd[1]: sysinit.target: Found dependency on ipset-init.service/start
[ 3.677165] systemd[1]: sysinit.target: Found dependency on basic.target/start
[ 3.678951] systemd[1]: sysinit.target: Found dependency on sockets.target/start
[ 3.680684] systemd[1]: sysinit.target: Found dependency on cloud-init-hotplugd.socket/start
[ 3.682663] systemd[1]: sysinit.target: Found dependency on sysinit.target/start
[ 3.684421] systemd[1]: sysinit.target: Job cloud-init.service/start deleted to break ordering cycle starting with sysinit.target/start

Is the Before=sysinit.target needed in cloud-init.service file?

Tags: systemd
Revision history for this message
Brett Holman (holmanb) wrote :

Hi Carlos,

Thank you for reporting this error. We will need more information to triage this problem.

Which distro, image, and platform are you running cloud-init on?

Please run `sudo cloud-init collect-logs` and upload the tarball here.

Changed in cloud-init:
status: New → Incomplete
Revision history for this message
Carlos F. (acsfer) wrote :

Hi Brett,

this happens on all my (cloud, KVM based) instances of Ubuntu 22.04.

Tarball here attached. Line 739 of dmesg file is what i'm talking about.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cloud-init because there has been no activity for 60 days.]

Changed in cloud-init:
status: Incomplete → Expired
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.