Incomplete backups sometimes not cleared on failure
Bug #1205471 reported by
Ed Cranford
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Fix Released
|
Undecided
|
Ed Cranford | ||
Bug Description
RAX operations staff have requested a method to immediately stop and fail backups on instances that are otherwise already failed for whatever reason. It would seem the easiest place to add this functionality is by augmenting the existing management call to reset the task status of an instance, as that's often the first step in stopping and recovering an unresponsive instance mid-build or mid-backup.
| Changed in trove: | |
| assignee: | nobody → Ed Cranford (ed--cranford) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to trove (master) | #1 |
| Changed in trove: | |
| status: | In Progress → Fix Committed |
| Changed in trove: | |
| milestone: | none → havana-3 |
| status: | Fix Committed → Fix Released |
| Changed in trove: | |
| milestone: | havana-3 → 2013.2 |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit f4530b0cd465629
Author: Ed Cranford <email address hidden>
Date: Fri Jul 12 16:52:01 2013 -0500
Clear new or building backups on reset-task-status
The reset-task-status management call now also clears off
any new or building backups for the instance by marking
those backups as FAILED.
Fixes Bug # 1205471
Change-Id: I478782b5e90c99