It is the correct URL to localhost as it is just making sure the engine health is up, it uses localhost as the playbook delegate to the engine VM so it is localhost.
He received a status code of 500 back, which means he was hit by the postgresql-jdbc bug and should downgrade.

I just don't understand why the oVIrt project does not release an async release just to handle this, this is a critical issue for many people, and especially new users trying to deploy oVirt for the first time, they will hit this bug immediately.

On Sat, Apr 30, 2022 at 1:53 PM Strahil Nikolov via Users <users@ovirt.org> wrote:
I think this is the problem:

"url": "http://localhost /ovirt-engine/services/health"

I believe it should be :
http://oengine.servername.local/ovirt-engine/services/health

Best Regards,
Strahil Nikolov

My records on the DNS server are as follows. When I check with nslookup, there is no access problem.
db.servername.local
onode.servername.local.        IN      A      192.168.1.10
oengine.servername.local.      IN      A      192.168.1.20
db.192.168.1
10    IN    PTR    onode.servername.local.
20    IN    PTR    oengine.servername.local.

What exactly is the problem about?

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
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/users@ovirt.org/message/EB6AULCZV4EBWS6YPZKEGUA7HTYUKK73/

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
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/users@ovirt.org/message/VV5DMFHGOGTHLSGS6RHJPKY4X2T44AC7/