no event recorded for INIT_* resources
Bug #1319813 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Zane Bitter |
Bug Description
We have a resource that is getting stuck on INIT_COMPLETE. There are no events visible in event-list <stack> for that resource (or any others) for the INIT state - I'm wondering if this is deliberate or oversight (because - its hard to debug the problem using the API without such events).
Changed in heat: | |
milestone: | none → juno-3 |
Changed in heat: | |
assignee: | Steven Hardy (shardy) → nobody |
Changed in heat: | |
milestone: | juno-3 → juno-rc1 |
Changed in heat: | |
milestone: | juno-rc1 → kilo-1 |
Changed in heat: | |
milestone: | kilo-1 → kilo-2 |
Changed in heat: | |
milestone: | kilo-2 → next |
Changed in heat: | |
assignee: | Steven Hardy (shardy) → Zane Bitter (zaneb) |
Changed in heat: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is a similar issue to https:/ /bugs.launchpad .net/heat/ +bug/1273796, which I started looking at but haven't had time to revisit.
Basically we need to store the state regardless of what happens at INIT time, and probably generate an event via the storage of that state.
I guess it's more of a historical known issue than an oversight, because "INIT" was never really a thing until https:/ /review. openstack. org/#/c/ 36385/ landed a while back.
Before then, the first transition was from the resource not existing to CREATE_IN_PROGRESS, but since then we have a slightly weird interim state which is unrelated to the state of the actual thing backing the resource.
I'll see if I can get back to 1273796 soon and solve it in a way which also fixes this.