Mistakingly and historically
tripleo.baremetal_deploy.v1.deploy_instances used to pass its
timeout input into ansible connection timeout instead of
global/deployment timeout.
To pertain the established tradition for setting connection timeout to
some timeout, add missing input for ansible connection timeout and give
it some reasonable value.
The use of the timeout input to be passed into the real deployment
timeout parameter is fixed in the scope of the related bug.
Reviewed: https:/ /review. opendev. org/717192 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=217deba8419 739efb9f43f840f 981d57920eff44
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit 217deba8419739e fb9f43f840f981d 57920eff44
Author: Bogdan Dobrelya <email address hidden>
Date: Thu Apr 2 14:45:15 2020 +0200
Add ssh timeout for baremetal_deploy
Mistakingly and historically baremetal_ deploy. v1.deploy_ instances used to pass its deployment timeout.
tripleo.
timeout input into ansible connection timeout instead of
global/
To pertain the established tradition for setting connection timeout to
some timeout, add missing input for ansible connection timeout and give
it some reasonable value.
The use of the timeout input to be passed into the real deployment
timeout parameter is fixed in the scope of the related bug.
Related-Bug: #1868063
Change-Id: I7d2fce9f07c98b 1770c01cacbae2d 17b8e143b3b 6dd3191956ed2bf 2f05f3b0e1)
Signed-off-by: Bogdan Dobrelya <email address hidden>
(cherry picked from commit 3d3afa62dc39223