In case of cluster_usage_timeout cluster is not going to None state

Bug #1507051 reported by Sushil Kumar on 2015-10-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Craig Vyvial

Bug Description

when cluster_usage_timeout occurs it updates the instances state to error state but does not resets the cluster state.

Changed in trove:
assignee: nobody → Sushil Kumar (sushil-kumar2)
status: New → In Progress
Changed in trove:
assignee: Sushil Kumar (sushil-kumar2) → Craig Vyvial (cp16net)
Craig Vyvial (cp16net) on 2016-03-25
Changed in trove:
importance: Undecided → Low
milestone: none → newton-1
Changed in trove:
assignee: Craig Vyvial (cp16net) → Amrith (amrith)
Amrith Kumar (amrith) on 2016-04-16
Changed in trove:
assignee: Amrith (amrith) → Craig Vyvial (cp16net)

Change abandoned by amrith (<email address hidden>) on branch: master
Reason: per trove meeting, August 10th, this is being abandoned for inactivity. If you want to continue work on this you can restore it.

Amrith Kumar (amrith) on 2016-09-18
Changed in trove:
milestone: newton-1 → ongoing
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers