Resources depending on conditioned resources are created before the dependencies of the conditioned resources are completed

[Giulio Fidente]

In a dependency chain like "A < B < C" where B is optional (conditioned), C is created before A is complete.

I am attaching a reproducer, after the stack is complete, the even list shows that Second is created before (or together with) First.

[Thomas Herve (therve)]

Yeah that's expected. When you depend on something not created, we ignore the error (since recently), but we don't go up the dep chain. You need to add the dependency explicitly yourself.

[Giulio Fidente (gfidente)]

hi Thomas, thanks again. We were indeed discussing with Steven on IRC if this is (or not) the intended behavior!

[Steven Hardy (shardy)]

This is really inconvenient for template authors though - I wonder if we should consider changing how conditionally defined resources work - what if we forced their type to OS::Heat::None when the condition is false, then the chain of dependencies and other weird corner cases related to skipping the node in the graph could be avoided?

[Thomas Herve (therve)]

It would somewhat change the expected behaviour. We could change the pike behavior, as the condition parsing is template specific. We may need to check the impact, though.