Hi everyone,

I'm trying to deploy a hyperconverged ovirt cluster, but the the wizard in 
cockpit failed at the first step with the error "FQDN is not reachable".

The goal is to have 3 nodes, with hosted engine on gluster FS.

Here is the relevant information :
- CentOS 8.4
- ovirt 4.4.8
- 2 network interfaces (1 for storage, 1 for production)

The packages installed : cockpit-ovirt-dashboard, vdsm-gluster, ovirt-host, 
ovirt-engine-appliance, gluster-ansible-roles

# rpm -qa | grep ovirt 
ovirt-imageio-client-2.2.0-1.el8.x86_64
ovirt-host-dependencies-4.4.8-1.el8.x86_64
ovirt-vmconsole-1.0.9-1.el8.noarch
python3-ovirt-setup-lib-1.3.2-1.el8.noarch
ovirt-provider-ovn-driver-1.2.34-1.el8.noarch
ovirt-host-4.4.8-1.el8.x86_64
ovirt-vmconsole-host-1.0.9-1.el8.noarch
ovirt-imageio-daemon-2.2.0-1.el8.x86_64
ovirt-hosted-engine-ha-2.4.8-1.el8.noarch
ovirt-hosted-engine-setup-2.5.3-1.el8.noarch
ovirt-engine-appliance-4.4-20210826223909.1.el8.x86_64
cockpit-ovirt-dashboard-0.15.1-1.el8.noarch
python3-ovirt-engine-sdk4-4.4.15-1.el8.x86_64
ovirt-ansible-collection-1.6.2-1.el8.noarch
ovirt-imageio-common-2.2.0-1.el8.x86_64

I didn't use the ovirt44-release package because we have to use our local repo. 
So we have cloned all necessary repo.
Every package installation was passed without any issues.

The /etc/hosts contains every FQDN/IP for the storage network (which is not 
exposed to the public), and the DNS server is reachable to respond to public 
FQDN.

Passwordless connection is installed and works perfectly with sotrage and 
production FQDN.

If you need more information, please tell me.

Thanks in advance for your help.
Regards
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/MJP35LJKTSPZSMOB5YD3OJMCSCS2M5FF/

Reply via email to