[HEAT] Sahara fails to rollback if stack in 'Failed' state

Bug #1337006 reported by Andrew Lazarev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sahara
Fix Released
Medium
Andrew Lazarev

Bug Description

Step to repro:
1. Create cluster
2. Create nodegroup with volume exceeding quota
3. Scale cluster adding nodegroup created in step 2

Expected result:
Sahara fails to scale and rollback cluster

Observed result:
Cluster in Error state

Probably problem related to <"disable_rollback": true> parameter in heat request.

Changed in sahara:
milestone: none → juno-3
Changed in sahara:
assignee: nobody → Andrew Lazarev (alazarev)
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to sahara (master)

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

Changed in sahara:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to sahara (master)

Reviewed: https://review.openstack.org/105321
Committed: https://git.openstack.org/cgit/openstack/sahara/commit/?id=11d283011749406d15751a55e34969294dd8060c
Submitter: Jenkins
Branch: master

commit 11d283011749406d15751a55e34969294dd8060c
Author: Andrew Lazarev <email address hidden>
Date: Mon Jul 7 18:35:49 2014 -0700

    Fixed cluster rollback on scaling with heat engine

    We can't allow stack to move into Error state if we want to use it futher.
    disable_rollback parameter controlls such behavior. It is Ok to have errored
    stack for cluster create and rollback since we will not be using it anyway. But
    for scaling we need to keep it Active since we can just rollback in case of
    error.

    Change-Id: Iab1a58f4924ca6a7689060f71217956a72316517
    Closes-Bug: #1337006

Changed in sahara:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in sahara:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in sahara:
milestone: juno-3 → 2014.2
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.