← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1880734] Re: ordering cycle upon booting groovy

 

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3698

** Bug watch added: github.com/canonical/cloud-init/issues #3698
   https://github.com/canonical/cloud-init/issues/3698

** Changed in: cloud-init
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1880734

Title:
  ordering cycle upon booting groovy

Status in cloud-init:
  Expired
Status in subiquity:
  New

Bug description:
  May 26 15:27:19 ubuntu-server systemd[1]: multi-user.target: Found ordering cycle on getty.target/start
  May 26 15:27:19 ubuntu-server systemd[1]: multi-user.target: Found dependency on serial-getty@sclp_line0.service/start
  May 26 15:27:19 ubuntu-server systemd[1]: multi-user.target: Found dependency on cloud-final.service/start
  May 26 15:27:19 ubuntu-server systemd[1]: multi-user.target: Found dependency on multi-user.target/start
  May 26 15:27:19 ubuntu-server systemd[1]: multi-user.target: Job getty.target/start deleted to break ordering cycle starting with multi-user.target/start

  
  We shall not have dependency cycles.

  Looks like we ordered getty.target to be both before and after multi-
  user.target via cloud-final & serial-getty service (getty.target)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1880734/+subscriptions



References