Cue

Create Cluster flow does not abort on ERROR VM Status

Bug #1522633 reported by Davide Agnello
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cue
Fix Released
Low
Sharika

Bug Description

While waiting for VMs to go ACTIVE during the create cluster flow, if one or more VMs go into ERROR state the VM check task continues until it times out. If one or more VM(s) go into ERROR state, the flow should be abort instead of waiting for that VM to go into ACTIVE state.

Changed in cue:
assignee: nobody → Sharika (sharika-pongubala)
Changed in cue:
status: New → In Progress
Min Pae (sputnik13)
Changed in cue:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cue (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cue (master)

Reviewed: https://review.openstack.org/255473
Committed: https://git.openstack.org/cgit/openstack/cue/commit/?id=6d1bc2ab063c2945286d6129f774eae92e81192a
Submitter: Jenkins
Branch: master

commit 6d1bc2ab063c2945286d6129f774eae92e81192a
Author: pongubal <email address hidden>
Date: Wed Dec 9 12:10:57 2015 -0800

    Abort VM Status flow when VM(s) go to ERROR state

    While waiting for VMs to go ACTIVE during the create cluster flow,
    if one or more VMs go into ERROR state the VM check task continues
    until it times out. If one or more VM(s) go into ERROR state, the flow
    should be abort instead of waiting for that VM to go into ACTIVE state.

    Change-Id: I9e3768c5a55803afe05f75fad41ecf74471b4694
    Closes-Bug: 1522633

Changed in cue:
status: In Progress → Fix Released
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.