openstack
/
cue
Code Issues Proposed changes

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
This commit is contained in:
Min Pae 2015-06-09 21:07:20 -07:00
parent ce8e1d22c1
commit a8a67b2007
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
cue/taskflow/flow/create_cluster_node.py
View File

@ -165,7 +165,7 @@ def create_cluster_node(cluster_id, node_number, node_id, graph_flow,
provides="node_values_%d" % node_number
)
graph_flow.add(build_node_info)
graph_flow.link(check_rabbit_online, build_node_info)
graph_flow.link(get_vm_id, build_node_info)
update_node = cue_tasks.UpdateNode(
name="update node %s" % node_name,