Heat SoftwareDeployments across provider resources
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Steve Baker |
Bug Description
As discussed with shardy and sbaker:
I think there are a couple of bugs in Icehouse around what happens when an OS::Nova::Server, OS::Heat:
The following scenarios work for me:
1) OS::Nova::Server, OS::Heat:
2) OS::Nova::Server, OS::Heat:
These two scenarios DON'T work for me:
3) OS::Nova::Server, OS::Heat:
4) OS::Nova::Server in one provider resource (let's call it Library::Server), OS::Heat:
In both cases 3 and 4, the problem is that the 'deployments' list returned to the instance when it polls the CFN API never grows to contain the relevant deployment objects, at which point it's game over.
I guess that there's some missing wiring in the CFN API backend for DescribeStackRe
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Steve Baker (steve-stevebaker) |
Changed in heat: | |
milestone: | none → juno-3 |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | juno-3 → 2014.2 |
I've just confirmed the following combination works as expected:
* config and deployment in a provider resource
* server and provider resource in the base template
Will try other combinations next