Instance shows ACTIVE after is has been stopped through nova API

Bug #1340383 reported by Greg Lucas on 2014-07-10
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Wishlist
Nikhil Manchanda

Bug Description

If a trove instance is stopped (via nova) it should not appear as ACTIVE in the trove list.

Greg Lucas (glucas-q) on 2014-07-10
Changed in trove:
assignee: nobody → Greg Lucas (glucas-q)
Denis M. (dmakogon) on 2014-07-10
Changed in trove:
status: New → Confirmed
Denis M. (dmakogon) wrote :

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/FAILED/ERROR ?

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
Amrith Kumar (amrith) wrote :

Updating importance to "Wishlist" (bugscrub, 2014-10-23)

This change will require a blueprint.

Changed in trove:
importance: Medium → Wishlist
Changed in trove:
status: Confirmed → Triaged
Changed in trove:
assignee: Greg Lucas (glucas-q) → Nikhil Manchanda (slicknik)
Amrith Kumar (amrith) wrote :

Nikhil, any updates on this?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers