yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1621075@xxxxxxxxxxxxxxxxxx>]

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

** 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/1621075

Title:
  Allow console login is possible when cloud-init fails to run

Status in cloud-images:
  Expired
Status in cloud-init:
  Expired

Bug description:
  We are currently investigating how to improve our handling of failures
  during enlistment and commissioning. This bug discusses the situation
  where the boot process did correctly kick off, but cloud-init itself
  failed to correctly start; for instance, the network configuration may
  be incorrect or incomplete.

  The first instinct when there is a failure is to log into the machine,
  but unfortunately that's not currently possible, because there are no
  credentials enabled on the machine. That makes debugging these
  failures particularly difficult.

  Could we detect that cloud-init has failed to run and enable console
  login, perhaps analogously to what happens when Ubuntu fails to mount
  the root filesystem?

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