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

[Saurabh Surana]

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.

[Illia Khudoshyn (ikhudoshyn)]

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.

[Michael Basnight (hubcap)]

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

[Denis M. (dmakogon)]

+1 to hub_cap

[Sushil Kumar (sushil-kumar2)]

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

[OpenStack Infra (hudson-openstack)]

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

[Denis M. (dmakogon)]

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

[OpenStack Infra (hudson-openstack)]

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

[Nikhil Manchanda (slicknik)]

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

[Amrith Kumar (amrith)]

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

[OpenStack Infra (hudson-openstack)]

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