InvalidInstanceID.NotFound
Bug #1457092 reported by
Aaron Bentley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
juju-core |
Won't Fix
|
Medium
|
Unassigned | ||
1.22 |
Won't Fix
|
Medium
|
Unassigned | ||
1.24 |
Won't Fix
|
Medium
|
Unassigned | ||
1.25 |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Juju bootstrapping will occasionally fail with "refreshing addresses: The instance ID 'i-003b92ff' does not exist (InvalidInstanc
Seen in: http://
It appears that AWS has created the instance but some parts of AWS are out-of-sync, so that requests using that instance ID do no immediately succeed. It seems likely that juju could retry to resolve this problem.
Changed in juju-core: | |
status: | New → Incomplete |
tags: | added: bootstrap |
Changed in juju-core: | |
status: | Incomplete → Triaged |
importance: | Undecided → Medium |
description: | updated |
information type: | Private → Public |
Changed in juju-core: | |
status: | Triaged → Invalid |
status: | Invalid → Triaged |
affects: | juju-core → juju |
Changed in juju-core: | |
importance: | Undecided → Medium |
status: | New → Won't Fix |
To post a comment you must log in.
Can also happen when tagging instances: reports. vapour. ws/releases/ 2703/job/ aws-charm- store-staging- deploy/ attempt/ 179
http://