Red Hat Bugzilla – Bug 1279544
Nested stack remains IN_PROGRESS even though none of its resources are IN_PROGRESS
Last modified: 2016-04-27 00:41:42 EDT
I hit this when testing OSP-d updates. One of the nested stacks is in UPDATE_IN_PROGRESS, even though all of its resources are UPDATE_COMPLETE or CREATE_COMPLETE.
heat-engine.log is rapidly flooding with the same lines, related to resource registry. There's also an error in heat-engine journal but that showed up during a single occasion, it's not appearing repeatedly.
[root@instack ~]# yum list installed | grep heat
heat-cfntools.noarch 1.2.8-2.el7 @rhelosp-7.0-puddle
openstack-heat-api.noarch 2015.1.1-7.el7ost @rhelosp-7.0-puddle
openstack-heat-api-cfn.noarch 2015.1.1-7.el7ost @rhelosp-7.0-puddle
openstack-heat-common.noarch 2015.1.1-7.el7ost @rhelosp-7.0-puddle
openstack-heat-engine.noarch 2015.1.1-7.el7ost @rhelosp-7.0-puddle
python-heatclient.noarch 0.6.0-1.el7ost @rhelosp-7.0-puddle
Created attachment 1091875 [details]
heat CLI queries
Created attachment 1091876 [details]
Created attachment 1091877 [details]
INFO logs about the resource registry are normal on any command that loads the stack.
The log in the journal appears to occur only during the undercloud update, when RabbitMQ is not reachable.
After some debugging on the box, I discovered that there were hooks set, and this was the reason that the update was not proceeding. This was likely caused by a previous operation, so I'm closing this as a duplicate of bug 1267558.
*** This bug has been marked as a duplicate of bug 1267558 ***