ec2: provisioning machines sometimes fails with "tagging instance: The instance ID <ID> does not exist"
Bug #1474788 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
| 1.24 |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
Tagging was added to Juju 1.24. Sometimes tagging fails right after the instance is created, because eventual consistency.
```
machines:
...
"5":
agent-
(
instance-id: pending
life: dead
series: trusty
```
We need to change the tagging code to retry for a short time after creating the instance.
| Changed in juju-core: | |
| milestone: | 1.24.3 → 1.25.0 |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| assignee: | nobody → Andrew Wilkins (axwalk) |
Revision history for this message
| John George (jog) wrote | #1 |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Peter Matulis (petermatulis) wrote | #2 |
To post a comment you must log in.
This looks like an instance of the the tagging still failing during bootstrap: http://