9c602da452
Fix misused ansible connection timeout and deployment timeout passed in config download and ansible runner utility. Allow ansible runner utility to be given a job_timeout as well. Also fix the misuse of timeout parameters in related worklows. Add --overcloud-ssh-port-timeout and use it to configure ansible connection timeout for the DeleteNode interace of the involved workflows. Then use the timeout parameter as real timeout instead of mistakingly passing it as a connection timeout. Add new unit test for ansible timeout in config_download. Add missing coverage for the existing timeout-related params in other unit tests. Closes-Bug: #1868063 Co-authored-by: Kevin Carter <kevin@cloudnull.com> Change-Id: I2a4d151bcb83074af5bcf7d1b8c68d81d3c0400d Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
12 lines
430 B
YAML
12 lines
430 B
YAML
---
|
|
features:
|
|
- |
|
|
`openstack overcloud node delete` now can take
|
|
`--overcloud-ssh-port-timeout` to configure connection timeout
|
|
for Ansible. While `--timeout` configures the command timeout as expected.
|
|
fixes:
|
|
- |
|
|
Ansible connection timeout used for config download and the deployment
|
|
timeout now will be given proper values. It fixes `bug 1868063
|
|
<https://bugs.launchpad.net/tripleo/+bug/1868063>`__.
|