Instance shows ACTIVE after is has been stopped through nova API
Bug #1340383 reported by
Greg Lucas
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Triaged
|
Wishlist
|
Nikhil Manchanda | ||
Bug Description
If a trove instance is stopped (via nova) it should not appear as ACTIVE in the trove list.
| Changed in trove: | |
| assignee: | nobody → Greg Lucas (glucas-q) |
| Changed in trove: | |
| status: | New → Confirmed |
Revision history for this message
| Denis M. (dmakogon) wrote | #1 |
| summary: |
- Instance shows ACTIVE after is has been stopped + Instance shows ACTIVE after is has been stopped through nova API |
| Changed in trove: | |
| importance: | Undecided → Medium |
| milestone: | none → juno-3 |
| Changed in trove: | |
| milestone: | juno-3 → ongoing |
Revision history for this message
| Amrith Kumar (amrith) wrote | #2 |
| Changed in trove: | |
| importance: | Medium → Wishlist |
| Changed in trove: | |
| status: | Confirmed → Triaged |
| Changed in trove: | |
| assignee: | Greg Lucas (glucas-q) → Nikhil Manchanda (slicknik) |
Revision history for this message
| Amrith Kumar (amrith) wrote | #3 |
To post a comment you must log in.
What about adding periodic task to conductor service that will iterate over all provisioned instances and check compute instance status (guest status can be defined only directly asking guest or adding new guest API call that will be used by conductor to perform force update for guest statuses) and if compute instance is Stopped/Deleted - mark guest as SHUTDOWN/