[2.8] Juju fails to connect to instance after juju-clean-shutdown.service timeout in cloud-init
Bug #1878639 reported by
Joshua Genet
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Joseph Phillips | ||
cloud-init |
Expired
|
Undecided
|
Unassigned |
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:/
tags: |
added: cdo-release-blocker removed: cdo-qa-blocker |
tags: |
added: foundations-engine removed: cpe-foundation |
Changed in juju: | |
status: | Incomplete → New |
summary: |
- [2.8] Juju fails to connect to AWS instance + [2.8] Juju fails to connect to instance after juju-clean- + shutdown.service timeout in cloud-init |
Changed in juju: | |
status: | New → Invalid |
Changed in juju: | |
status: | Invalid → New |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Joseph Phillips (manadart) |
milestone: | none → 2.8.1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
tags: | removed: cdo-release-blocker |
To post a comment you must log in.
I spun up a happy aws controller and deployed a unit. Nothing like a k8s config, but I see the same EC2 errors in the /var/log/amazon/ssm files.