app-delete-receiving-stack-not-found

[Devdatta Kulkarni]

When we try to redeploy an already deployed app, we delete the previous heat stacks associated with the app. In the solum-deployer screen we are seeing this stack trace:

{"explanation": "The resource could not be found.", "code": 404, "error": {"message": "The Stack (abc-df8fae1e-9388-4230-8be0-a7893417716c) could not be found.", "traceback": "Traceback (most recent call last):\n\n File \"/opt/stack/heat/heat/common/context.py\", line 329, in wrapped\n return func(self, ctx, *args, **kwargs)\n\n File \"/opt/stack/heat/heat/engine/service.py\", line 455, in identify_stack\n raise exception.EntityNotFound(entity='Stack', name=stack_name)\n\nEntityNotFound: The Stack (abc-df8fae1e-9388-4230-8be0-a7893417716c) could not be found.\n", "type": "EntityNotFound"}, "title": "Not Found"}
 log_http_response /usr/local/lib/python2.7/dist-packages/heatclient/common/http.py:142
2016-02-22 16:30:08.718 26555 DEBUG solum.deployer.handlers.heat [-] Heat stack deleted 997d66d9-24ac-45c8-a8d9-bd333f1d69b7 _destroy_other_assemblies /opt/stack/solum/solum/deployer/handlers/heat.py:328
2016-02-22 16:30:08.719 26555 DEBUG heatclient.common.http [-] curl -g -i -X GET -H 'X-Auth-Token: {SHA1}31f550ec3a12263eec1b1a2f58fecf0ec4f81c9f' -H 'Content-Type: application/json' -H 'X-Auth-Url: http://10.0.2.15:5000/v3' -H 'Accept: application/json' -H 'User-Agent: python-heatclient' http://10.0.2.15:8004/v1/40a4b85c5d7d470b87e8e99e254a9bbe/stacks/abc-df8fae1e-9388-4230-8be0-a7893417716c log_curl_request /usr/local/lib/python2.7/dist-packages/heatclient/common/http.py:129
2016-02-22 16:30:08.882 26555 DEBUG heatclient.common.http [-]
HTTP/1.1 404 Not Found

solum-deployer seems to be stuck trying to delete the heat stack.
The deployer eventually picks up subsequent deployment message, but it seems to be trying to delete the heat stack for some number of attempts,
instead of moving on (failing fast), if a heat stack is not found.

[Vijendar Komalla (vijendar-komalla)]

Hi Dev,
I believe this was fixed as part of https://review.openstack.org/#/c/280986/ , so marking it as Fixed.
Please feel free to mark it as 'New' if you are still seeing this issue.

Thanks,