As RockyLinux seems to have postgresql-jdbc-42.2.3-3.el8_2, you
shouldn't be hitting the major bug currently. Also you are using oVirt
4.4 and shouldn't be hitting the ansible-core issue either.
I'm afraid we'll need more info from your logs to give you any help.
-Patrick Hibbs
On Sat,
Good morning.
I have an hosted engine in my VM cluster that fails to start after upgrading
from 4.4.9 to 4.4.10.
Looking at the ovirt-enginge boot.log, I can see the following:
06:19:46,860 ERROR [org.jboss.as.controller.management-operation] WFLYCTL0013:
Operation ("add") failed - address:
Problem solved. Reason was a fail at engine-setup.
Engine setup showed cluster not in Global Maintenance mode, even if the cluster
was indeed in Global Maintenance. Had to force engine setup by using a hint
from https://www.ovirt.org/media/Hosted-Engine-4.3-deep-dive.pdf, Major issues
4.
This bug also affects non-hyperconverged Gluster volumes run by Debian
hosts. (Debian uses Gluster 9. Specifically glusterfs-server 9.2-1.)
Funnily enough, Gluster 9 is compatible with both oVirt 4.4 and 4.5.
With no changes required on the Gluster side at all. So it seems that
this bug is purely
I'm attempting a 4.4.9 install on Rocky 8.5, and getting the same errors.
Any insight on this error
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement:
It's most probably the postgresql-jdbc issue.Connect to the engine over ssh and
downgrade the 'postgresql-jdbc' package.
Best Regards,Strahil Nikolov
On Sun, May 1, 2022 at 9:39, gantonjo-ovirt--- via Users
wrote: Good morning.
I have an hosted engine in my VM cluster that fails to start
6 matches
Mail list logo
