Magnum

After the delete bay fails we can do nothing

Bug #1535230 reported by space
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
New
Medium
rajiv

Bug Description

  After the delete bay fails,the bay's status becomes "DELETE FAILED" .And I don't know how to delete the bay again.Delete the bay from the database may be the only way.I think it is not friendly to us.

Revision history for this message
Tom Cammann (tom-cammann) wrote :

Magnum could issue a heat stack abandon or delete the bay from the database.

Changed in magnum:
status: New → Invalid
status: Invalid → In Progress
status: In Progress → New
importance: Undecided → Medium
rajiv (rajiv-kumar)
Changed in magnum:
assignee: nobody → rajiv (rajiv-kumar)
Revision history for this message
rajiv (rajiv-kumar) wrote :

@Tom,
Do you mean some periodic job must run and delete the bay from the database if bay is in failed state?
or do you mean something else?

Revision history for this message
Vijendar Komalla (vijendar-komalla) wrote :

is this still an issue? I was not able to reproduce the problem.
I was able to delete delete_failed cluster by re-running cluster-delete command. If magnum abandons the delete failed stack, it leaves some resource behind and probably that is not a good idea. If re-running cluster-delete doesn't work, can try following
1. manually delete failed/error resource and re-run cluster-delete
2. OR delete all the cluster resources manually then abandon the cluster stack and re-run cluster-delete

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.