app-delete-receiving-stack-not-found
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Solum |
Fix Committed
|
Critical
|
Vijendar Komalla |
Bug Description
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-
log_http_response /usr/local/
2016-02-22 16:30:08.718 26555 DEBUG solum.deployer.
2016-02-22 16:30:08.719 26555 DEBUG heatclient.
2016-02-22 16:30:08.882 26555 DEBUG heatclient.
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.
Changed in solum: | |
milestone: | none → next-mitaka |
importance: | Undecided → Critical |
description: | updated |
Changed in solum: | |
assignee: | nobody → Vijendar Komalla (vijendar-komalla) |
Hi Dev, /review. openstack. org/#/c/ 280986/ , so marking it as Fixed.
I believe this was fixed as part of https:/
Please feel free to mark it as 'New' if you are still seeing this issue.
Thanks,