← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1878639] Re: [2.8] Juju fails to connect to instance after juju-clean-shutdown.service timeout in cloud-init

 

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

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

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

Title:
  [2.8] Juju fails to connect to instance after juju-clean-
  shutdown.service timeout in cloud-init

Status in cloud-init:
  Expired
Status in Canonical Juju:
  Fix Released

Bug description:
  AWS does spin up an instance and assigns an IP, but Juju stays stuck in Pending.
  There's a bunch of EC2RoleRequest EC2Metadata Errors in the controller logs.

  Here's a link to the logs/artifacts:
  https://oil-jenkins.canonical.com/artifacts/5e61db53-50f0-4b82-9bb1-957bd0085d46/index.html

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