fails to notice (or retry) if there's an error connecting to launchpad
Bug #1158841 reported by
Tom Haddon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
We recently had a juju instance stuck in "agent-state: pending". Digging into the logs it turned out it was a failure to connect to launchpad to get the version of juju required, and a failure to notice this and retry:
http://
Retrying again with a new instance worked fine.
Cloud-init should notice if it fails to connect to launchpad in this case, and retry before failing hard.
| tags: | added: canonical-webops |
| tags: |
added: canonical-webops-juju removed: canonical-webops |
| tags: |
added: canonical-webops removed: canonical-webops-juju |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| importance: | High → Low |
To post a comment you must log in.
My mistake, seems this is in juju itself, not cloud-init.