Cue

resources not cleaned up when deleting a cluster in BUILDING state

Bug #1452990 reported by Min Pae
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cue
Fix Committed
Medium
Unassigned

Bug Description

When a cluster that is stuck in BUILDING (like in https://bugs.launchpad.net/cue/+bug/1452958) is deleted, the resources (VMs in my specific case) that were created are never cleaned up. This is likely because the VM ID is never recorded until the VM goes ACTIVE. It seems like it would be better to record the resource ID once it's created rather than depending on its state to change to an acceptable state before anything is recorded.

Min Pae (sputnik13)
Changed in cue:
importance: Undecided → Medium
importance: Medium → Undecided
Min Pae (sputnik13)
Changed in cue:
importance: Undecided → Medium
Revision history for this message
Min Pae (sputnik13) wrote :

Reviewed: https://review.openstack.org/190014
Committed: https://git.openstack.org/cgit/stackforge/cue/commit/?id=a8a67b200719fc6bd5315fe7399b9119198fa1a9
Submitter: Jenkins
Branch: master

commit a8a67b200719fc6bd5315fe7399b9119198fa1a9
Author: Min Pae <email address hidden>
Date: Tue Jun 9 21:07:20 2015 -0700

    Moving Node update earlier in cluster create flow

    Moving Node update to happen earlier in the cluster create process, such
    that node VM ID is recorded regardless of cluster create success or
    failure so that any VMs created during a failed cluster create can be
    properly destroyed.

    Change-Id: I0c46e18986c615948300b145a9e68bc6607e13ec
    Closes-Bug: 1463605

Changed in cue:
status: New → Fix Committed
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.