Cue

node id is not recorded if provisioning does not complete

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

Bug Description

Node ID is not being recorded if a broker does not fully provision. This is an issue as trying to delete a cluster while it's building, or if the worker is interrupted, or if there is some failure such that the cluster is not rolled back during a cluster create, the node cannot be deleted along with the cluster.

Also, if the node ID does not exist Cue is issuing a nova delete with None as the ID, which causes an exception in novaclient.

Reproduction steps:
- create a cluster of size 3
- kill cue-worker
- launch zkCli
- rmr /cue/taskflow/jobs
- exit zkCli
- start cue-worker
- cluster status should stay in BUILDING after worker has consumed the job
- issue a cluster delete
- nova client will throw exceptions stating instance of type None cannot be found

Min Pae (sputnik13)
Changed in cue:
importance: Undecided → Medium
Min Pae (sputnik13)
description: updated
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cue (master)

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.

Other bug subscribers

Remote bug watches

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