deleteing an instance shouldn't need to stop the datastore first
Bug #1525428 reported by
Craig Vyvial
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
In Progress
|
Undecided
|
Unassigned | ||
Bug Description
When we are deleting a datastore i'm not sure there is a compelling reason to stop the datastore before starting to delete the resources. Many times on an ERROR instance this has to wait until the call times out before then going and deleting the instance resources.
| tags: | added: delete-instance-force |
| Changed in trove: | |
| assignee: | nobody → jian.song (jiansong) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to trove (master) | #1 |
| Changed in trove: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on trove (master) | #2 |
| Changed in trove: | |
| assignee: | jian.song (jiansong) → nobody |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/