update asg resource which in FAILED state shouldn't enter UpdateReplace flow
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
huangtianhua | ||
Juno |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
1. create a stack with template:
heat_template_
resources:
her_policy_group:
type: OS::Nova:
# A Nova ServerGroup
properties:
name: nova-server-group
policies: [affinity]
her_asg:
type: OS::Heat:
properties:
resource:
type: OS::Nova::Server
properties:
image: 74f50a38-
flavor: m1.tiny
min_size: 1
desired_
max_size: 11
2. the stack create successful, and the nova instances are all active
3. update the template, change desired_capacity to 7(exceed the quota 5)
4. update the stack
5. the stack is update failed, and there are 5 instances in group, and also nova list show 5 instances in active
6. update the stack again, change desired_capacity back to 3
7. then the resource 'her_asg' will enter the UpdateReplace flow, and to re-create instances, I think it's incorrect to re-create new instances.
Found that: if a resource in 'FAILED' state will enter the UpdateReplace flow, I'm thinking if the resource has nested_stack, we should enter the resource.update not the UpdateReplace flow.
Changed in heat: | |
importance: | Undecided → High |
milestone: | none → kilo-1 |
tags: | added: juno-backport-potential |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-1 → 2015.1.0 |
tags: | removed: juno-backport-potential |
the test depends on the change https:/ /review. openstack. org/#/c/ 129177/