Resource group with a nested wait condition handle fails on create
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Miguel Grinberg | ||
Juno |
Fix Released
|
High
|
Steven Hardy |
Bug Description
I'm launching a template that includes a ResourceGroup that points to a nested template. The nested template includes a wait condition handle resource, among other things. If the name of the wait condition handle resource is too long, then the creation of the resource group fails.
The log points out the problem clearly:
2014-12-16 02:51:34.276 WARNING heat.common.
...
2014-12-16 02:51:34.381 INFO heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
2014-12-16 02:51:34.381 TRACE heat.engine.
Changed in heat: | |
importance: | Undecided → Medium |
milestone: | none → kilo-2 |
tags: | added: juno-backport-potential |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-2 → 2015.1.0 |
tags: |
added: in-stable-juno removed: juno-backport-potential |
Reproduction templates:
slave.yaml:
heat_template_ version: 2013-05-23
resources: :WaitCondition
wait_condition:
type: OS::Heat:
properties:
handle: { get_resource: wait_handle }
count: 1
timeout: 600
wait_handle: :WaitConditionH andle
type: OS::Heat:
master.yaml:
heat_template_ version: 2013-05-23
resources: :ResourceGroup
cluster:
type: OS::Heat:
properties:
count: 2
resource_def:
type: slave.yaml
To reproduce, just run: heat stack-create test -f master.yaml