I use ansible to build a 3 node HCI environment, or at least I did with 4.4.6.
This fails every time with 4.5.2 - what broke?
Has anyone any idea what changed and if there's a simple resolution?
Kind Regards
Simon...
Show replies by date
Hi,
i had a similar issue yesterday, "Wait for the host to be up", on a 3 node HCI
gluster setup, using Lates ovirt-node.
The issue was that ansible/playbook failed to update temp private VM ip (from /etc/hosts,
created by ansible/hosted-engine), i received no error of this dyring the deployment via
ansible, had to dig engine logs.
I managed to fix the issue by changing the HostedEngine IP to FQDN manually via
"hosted-engine --console " and then restarting networking, after few seconds
deployment continued normally.
Hope this helps,
Andreas
Thanks Andreas.
I found my issue was caused by our nic bonding script.
I created the bonds via cockpit on each node first and then ran our build scripts
(omitting the nic bonding) and it worked first time.
Regards
Simon