Instance in backup status can be deleted which leaves the backup in NEW/BUILD state

Bug #1220989 reported by Saurabh Surana
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
In Progress
Low
Denis M.

Bug Description

Trove Instance on which Backup API is invoked can be deleted (even though the status of the instance has turned to BACKUP).

This leaves the backup in NEW/BUILD state, which can not be deleted.

Either we should not delete instance in BACKUP status, or when we delete the instance, if there is a backup for that instance in BUILD/NEW status, it should be marked as FAILED.

Revision history for this message
Illia Khudoshyn (ikhudoshyn) wrote :

Backup process may stall and it will leave a backup in NEW/BUILD state . It should not block an instance from removal. So the second way (mark backup as FAILED) is what I like more.

Revision history for this message
Michael Basnight (hubcap) wrote :

yes i like the mark backup as FAILED and allow delete.

Changed in trove:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Denis M. (dmakogon) wrote :

+1 to hub_cap

Changed in trove:
assignee: nobody → Denis M. (dmakogon)
status: Triaged → Confirmed
Changed in trove:
status: Confirmed → In Progress
Revision history for this message
Sushil Kumar (sushil-kumar2) wrote :

yeah, setting it to failed would help deletion of an invalid instance.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

Fix proposed to branch: master
Review: https://review.openstack.org/64156

Changed in trove:
assignee: Denis M. (dmakogon) → Sushil Kumar (sushil-kumar2)
Denis M. (dmakogon)
Changed in trove:
assignee: Sushil Kumar (sushil-kumar2) → Denis M. (dmakogon)
Revision history for this message
Denis M. (dmakogon) wrote :

Ok, so, decision was made: mark all running backups as FAILED and allow deleting of them

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/102838

Denis M. (dmakogon)
Changed in trove:
milestone: none → juno-3
Changed in trove:
milestone: juno-3 → juno-rc1
Revision history for this message
Nikhil Manchanda (slicknik) wrote :

Issue is not release critical to hold juno-rc1 for. Moving to kilo-1.

Changed in trove:
milestone: juno-rc1 → kilo-1
Revision history for this message
Amrith Kumar (amrith) wrote :

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

Changed in trove:
importance: Medium → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on trove (master)

Change abandoned by Denis M. (<email address hidden>) on branch: master
Review: https://review.openstack.org/102838

Changed in trove:
milestone: kilo-1 → ongoing
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers