Trove should move the instance to ERROR if the underlying instance is removed
Bug #1531625 reported by
Luigi Toscano
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
When an instance is stuck in BUILD state for same reason (configuration error, etc) it is not possible to recover it. This is another issue that should be checked, but the scope of this bug is more limited: when the instance is stuck in BUILD state, and the underlying instance is terminated calling nova directly, Trove never realizes that the instance should be moved in ERROR state, and it stays BUILD (at least in Liberty). The instance should move to ERROR after some timeout.
| Changed in trove: | |
| assignee: | nobody → Amrith (amrith) |
| tags: | added: delete-instance-force |
| Changed in trove: | |
| assignee: | Amrith (amrith) → nobody |
| status: | New → Confirmed |
To post a comment you must log in.
