51-hosts at scale fails to complete and does not report an error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Steven Hardy |
Bug Description
51-hosts fails to complete running, and wedges scale deployments from ever completing.
^ however there is no error.d directory on any of my hosts, nor do we see the error referenced.
Things would lock up like this : https:/
I would look at the host, and review the tmp directory : https:/
Note: we would never see stop_51-hosts
To get around this, I have modified the 51-hosts file to simply exit 0, to have my deployment move forward.
Which I do see:
2017-03-21 15:27:21Z [overcloud-
f4f4b succeeded
summary: |
- 51-hosts at scale fails to complete or report a bug + 51-hosts at scale fails to complete or report an error |
Changed in tripleo: | |
importance: | Critical → High |
milestone: | none → pike-2 |
summary: |
- 51-hosts at scale fails to complete or report an error + 51-hosts at scale fails to complete and does not report an error |
Changed in tripleo: | |
assignee: | nobody → Kambiz Aghaiepour (kambiz-e) |
status: | Triaged → In Progress |
Changed in tripleo: | |
assignee: | Kambiz Aghaiepour (kambiz-e) → Steven Hardy (shardy) |
Just a heads up that during Ocata release we stopped using 51-hosts in favor of a heat hook. This was required for the "composable undercloud" effort (for which I did not to implement signalling support for these old style elements).
The new hook is here: http:// git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ tree/scripts/ hosts-config. sh
If possible it might be worth trying to see if this could be helpful in the old environment using 51-hosts to give better error handling and signalling.