Comment 21 for bug 1389178

stevebaker: I don't think I entirely get it

so when I not patch heat, each configured node sends signal like this in 99-refresh-completed

http://192.0.2.1:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Abc1620a67879427f9fbda235d2558bc0%3Astacks%2Fovercloud-ComputeAllNodesDeployment-isqr55mpumd4%2F110b50b7-6dd7-44e2-b6d7-4d0861285691%2Fresources%2F0?Timestamp=2014-11-13T08%3A54%3A22Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=05e65a07fd364908a22b5b456c121a5e&SignatureVersion=2&Signature=IX7H8EzzxrYcQMt5A%2BdkFZ0Fs7l6Q4cjUTqpZd1xJDU%3D

which has encoded id of ComputeAllNodesDeployment = 110b50b7-6dd7-44e2-b6d7-4d0861285691
and resource_name=0

So this exactly tracks which node has been configured and completes the correct nested resource of ComputeAllNodesDeployment . That seems like a correct behavior to me.

So this still looks like heat bug to me, that sometimes the id of ComputeAllNodesDeployment is wrong, cause it creates new one in the meantime. Otherwise I would expect it to work like this.