Open drokath opened 3 years ago
The wait_for_connection in 03_engine_initial_tasks might be useless as all tasks executed with this playbook are delegated to the engine itself. If engine is not up no tasks can be executed. (See full_execution.yml and partial_execution.yml) Does anyone concur ?
Hi @drokath, makes sense, did you try to remove wait_for_connection in 03_engine_initial_tasks and check if the deployment succeeds?
I did but the wait is necessary as the engine boot can be quite long. If a static IP is provided why not set it directly with cloud-init ?
SUMMARY
When trying to deploy the engine from an ansible control node different from the hc_nodes, the application of hosted_engine_setup role can not go pass wait_for_connection.
As indicated in https://github.com/ansible/ansible/issues/36519 wait_for_connection can not be delegated for now
COMPONENT NAME
ovirt.ovirt.hosted_engine_setup File: 03_engine_initial_tasks.yml
STEPS TO REPRODUCE
EXPECTED RESULTS
Role should proceed to the next tasks. When connecting manually the VM does respond : ssh in node1.test.local then ssh in dhcp-leased ip
ACTUAL RESULTS