Hmm, it seems a bit wrong that NovaCompute1Config gets attributes of NovaCompute1, which is the thing is is configuring. But this whole LaunchConfiguration business is a hack anyway.
You _will_ need to get around it by having NovaCompute1 depend on the NovaCompute1CompletionHandle directly.
That said, based on IRC discussions, there is still a Heat bug to be addressed here, in that during an update the newly-created WaitCondition is not writable until after the update is complete, which is obviously too late.
(Apologies for setting the wrong status on this; I just assumed it was in the Heat component without looking.)
Hmm, it seems a bit wrong that NovaCompute1Config gets attributes of NovaCompute1, which is the thing is is configuring. But this whole LaunchConfiguration business is a hack anyway.
You _will_ need to get around it by having NovaCompute1 depend on the NovaCompute1Com pletionHandle directly.
That said, based on IRC discussions, there is still a Heat bug to be addressed here, in that during an update the newly-created WaitCondition is not writable until after the update is complete, which is obviously too late.
(Apologies for setting the wrong status on this; I just assumed it was in the Heat component without looking.)