stack is in a wrong state

Bug #1693985 reported by huangtianhua
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
In Progress
High
huangtianhua

Bug Description

1. create a stack with a heat autoscaling group
2. update the stack to change the size of the group manually, and rollback=true
3. something wrong when group scale, so nested stack enter rollback flow
4. the nested stack rollback successful, but the top stack is in UPDATE_FAILED

We set nested stack to UPDATE_FAILED before the nested stack entering rollback, and meanwhile the group check whether the nested stack update complete, and happened the UPDATE_FAILED.

Changed in heat:
assignee: nobody → huangtianhua (huangtianhua)
Changed in heat:
importance: Undecided → High
milestone: none → pike-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

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

Changed in heat:
status: New → In Progress
Revision history for this message
Zane Bitter (zaneb) wrote :

Was this in a legacy stack or convergence?

Nested stacks should never rollback:

http://git.openstack.org/cgit/openstack/heat/tree/heat/engine/resources/stack_resource.py#n215

so it's strange that this one is.

Rico Lin (rico-lin)
Changed in heat:
milestone: pike-2 → pike-3
Rico Lin (rico-lin)
Changed in heat:
milestone: pike-3 → pike-rc1
Rabi Mishra (rabi)
Changed in heat:
milestone: pike-rc1 → pike-rc2
Rico Lin (rico-lin)
Changed in heat:
milestone: pike-rc2 → queens-1
Rico Lin (rico-lin)
Changed in heat:
milestone: queens-1 → pike-rc2
Rico Lin (rico-lin)
Changed in heat:
milestone: pike-rc2 → queens-1
Rico Lin (rico-lin)
Changed in heat:
milestone: queens-1 → queens-2
Rico Lin (rico-lin)
Changed in heat:
milestone: queens-2 → queens-3
Rico Lin (rico-lin)
Changed in heat:
milestone: queens-3 → queens-rc1
Rabi Mishra (rabi)
Changed in heat:
milestone: queens-rc1 → rocky-1
Rico Lin (rico-lin)
Changed in heat:
milestone: rocky-1 → rocky-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.