Do you use the same interface for gluster and ovirt node?
I had the same issue like you. I was trying to install HE deployment and it was always
failing. I was about to give up on ovirt then I decided to use separate interfaces for
network and storage traffic, and everything worked like a charm. You will still see some
pause when it is waiting for the host to be up, but it will work.
I am not sure but I believe that something happens during installation when using the
single interface. The bridge adapter for the engine never gets created.
Sent from my iPad
Sent from my iPad
On Jun 17, 2019, at 10:35 PM, nico.kruger(a)darkmatter.ae wrote:
Hi Guys,
I have tried installing oVirt 4.3.4 using
ovirt-node-ng-installer-4.3.4-2019061016.el7.iso and
ovirt-engine-appliance-4.3-20190610.1.el7.x86_64.rpm
Gluster install works fine, but HE deployment fails every time at last "waiting for
host to be up". I have tried the deployment on multiple different hardware types,
also tried single Vs 3 node deployments and all fail at the same point.
I suspect that the IP in the HE is not being correctly configured as i see qemu running,
but ansible times out and cleans up the fail install.
Any ideas on why this is happening? i will try add the logs
I am going to try using a older HE appliance rpm to see if that fixes the issue.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFZ2BBTI7MV...