Instances stuck in BUILD should time out by default
Bug #1339826 reported by
Greg Lucas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Medium
|
Greg Lucas |
Bug Description
When an instance fails to go ACTIVE after some amount of time, the default behavior should be to put the instance in an ERROR state.
This behavior exists but the default is to disable the time-out such that instances can remain stuck in BUILD forever. For new users this is confusing as there is not a straightforward way to clean out such instances.
This behavior is controlled by these options:
usage_timeout (default=400)
update_
Changed in trove: | |
assignee: | nobody → Greg Lucas (glucas-q) |
Changed in trove: | |
importance: | Undecided → Medium |
milestone: | none → juno-2 |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/105825
Review: https:/