- Users - oVirt List Archives

Re: could not start ovirt-engine: TagsDirector.init() fails
by Liebe, André-Sebastian 06 May '22

06 May '22

Donwngrading postgresql-jdbc from 42.2.14-1.el8 to 42.2.3-3.el8_2 (hint from failing ovirt 4.5 deployment https://lists.ovirt.org/archives/list/users@ovirt.org/thread/FA6BLIAIYY7GOX…) did the trick. > dnf downgrade postgresql-jdbc > systemctl restart ovirt-engine sincerely André-Sebastian Liebe Zukunftslabor gematik GmbH | Friedrichstr. 136 | 10117 Berlin Tel +49 30 40041-197 | Fax +49 30 40041-111 andre.liebe(a)gematik.de | www.gematik.de Amtsgericht Charlottenburg HRB 96351 Geschäftsführer: Dr. med Markus Leyck Dieken -----Ursprüngliche Nachricht----- Von: Liebe, André-Sebastian Gesendet: Freitag, 6. Mai 2022 07:46 An: users(a)ovirt.org Betreff: could not start ovirt-engine: TagsDirector.init() fails Hello list, I'm unable to start ovirt-engine after switching from CentOS 8 to CentOS 8-stream, doing a system update and a reboot. A previously done ovirt update from 4.4.9 to 4.4.10 (w/o system reboot but with service restart) went smoothly, so I guess it's somehow caused by one oft he centOS updates? The root cause logged in server.log reads: > org.springframework.dao.InvalidDataAccessApiUsageException: Unable to determine the correct call signature - no procedure/function/signature for 'gettagsbyparent_id' But according to ovirt-engine-setup-*.log a GettagsByparent_id(v_parent_id UUID) function ist created duging engine-setup (which I run after dnf update). When searching google for " org.ovirt.engine.core.bll.TagsDirector.init()" and "'gettagsbyparent_id" I got some results hinting for a faulty PosgreSQL jdbc driver from 2018 Any hints? sincerely André-Sebastian Liebe Zukunftslabor gematik GmbH | Friedrichstr. 136 | 10117 Berlin Tel +49 30 40041-197 | Fax +49 30 40041-111 andre.liebe(a)gematik.de | www.gematik.de Amtsgericht Charlottenburg HRB 96351 Geschäftsführer: Dr. med Markus Leyck Dieken

1 0

Virt group has no storage.owner-uid/gid anymore
by Strahil Nikolov 06 May '22

06 May '22

Hi All, is there any reason why the virt group is no longer having the storage.owner-uid & storage.owner-gid set to 36 ?I've opened an issue to track the reasons/bugfix at https://github.com/gluster/glusterfs/issues/3503 Best Regards,Strahil Nikolov

1 0

Re: [IMPORTANT] Upgrade to postgresql-jdbc-42.2.14-1 breaks oVirt Engine 4.4/4.5
by laj811＠gmail.com 05 May '22

05 May '22

I'm surprised this hasn't been fixed yet. This bug causes the engine setup on new node 4.5 installs to fail. Had I not found this post, I wouldn't have figured out what was going on during the engine setup process. This really needs to be fixed. -Lucas

1 0

ovirt engine restore: Failed to construct component instance
by Rafhael Almeida 05 May '22

05 May '22

Please your help, I restore a engine db correctly in a Fresh Installation on my same server: engine-backup --mode=restore --file=ovirt.2022-04-29_12h00.tar.gz --log=ovirt_log.2022-04-29_12h00.out --restore-permissions --provision-all-databases after engine-setup (I dont' see any warning o error, everything is correct) but when try to accces in my private domain, to access to ovirt-engine, don't work, I see in the files: /etc/ovirt-engine/engine.conf.d/10-setup-cinderlib-database.conf /etc/ovirt-engine/engine.conf.d/10-setup-database.conf /etc/ovirt-engine/engine.conf.d/10-setup-dwh-database.conf another password, in my last engine db, I have another passw to connect to db when i restart the service systemctl restart ovirt-engine y see this logs: *------------my server.log ----------------* Service status report WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance WFLYCTL0448: 2 additional services are down due to their dependencies being missing or failed 2022-05-04 16:09:25,234-05 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 2022-05-04 16:09:25,238-05 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 23.0.2.Final (WildFly Core 15.0.1.Final) started (with errors) in 15182ms - Started 1668 of 1888 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand) 2022-05-04 16:09:25,240-05 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2022-05-04 16:09:25,241-05 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706 *--------------------------------------------------* pd. my logs: https://filedn.com/lYVRQ0f0QUTQVmMCo3Bk7DY/server.log my ideas ran out, Please your help !!

2 2

Re: Ovirt 4.5.0.1 self-hosted deployment fails - jboss errors
by hans＠jiflin.nl 05 May '22

05 May '22

Hi, did you resolve this? I am trying to setup a new environment also and can't get past the errors anymore... > Hello, > > I’m trying to deploy a self-hosted engine on Ovirt node v4.5.0.1, but the deployment fails > in the final stages with the following errors in “Server.log” file. > > > I hope that you have an Idea about that. I ran the installer 3 times (cockpit installer. > > Thank you,

2 1

Async release for ovirt-engine (4.5.0.6) is now available
by Lev Veyde 04 May '22

04 May '22

The oVirt Team has just released a new version of ovirt-engine package (4.5.0.6) that fixes a few important bugs: - Bug 2055136 <https://bugzilla.redhat.com/2055136> - virt module is not changed to the correct stream during host upgrade - Bug 2074112 <https://bugzilla.redhat.com/2074112> - VM does not have a disk after restored from backup - Bug 2076465 <https://bugzilla.redhat.com/2076465> - OVA import: importing OVA of Q35/UEFI VM failed with 'Duplicate key nvram' The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Rebuilding Gluster Storage through GUI?
by Abe E 04 May '22

04 May '22

Is it possible to reconfigure my broken arbiter gluster from the GUI? Something broke it all in my 4.4 to 4.5 Upgrade after reboot and I just don't have the time to keep TSing through it versus attempting to rebuild it. Has anyone ever tried re-installing the node itself and using the ovirt gui to run in theory a single gluster install to add it to the main DC? This would save alot of configs through the CLI for rebuiling the bricks for this node.

2 3

Re: Self-hosted engine 4.5.0 deployment fails
by diego.ercolani＠ssis.sm 04 May '22

04 May '22

Please follow the instruction here: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/N6MNSV4ZK26V5N…

1 0

Unable to remove host from ovirt engine
by Joseph Gelinas 03 May '22

03 May '22

Recently our host and ovirt engine certificates expired and with some ideas from Strahil we were able to get 2 of the 3 ovirt hosts updated with usable certificates and move all of our VMs to those two nodes. https://lists.ovirt.org/archives/list/users@ovirt.org/thread/QCFPKQ3OKPOUV2… Not having any luck with the last host we figured we'd just try to remove it from ovirt engine and re-add it. While it seems `hosted-engine --vm-status` on one node no longer shows the removed host, the other good host and the web interface still show ovirt-1 in the mix. What is the best way to remove a NonRespnsive host from ovirt and re-add it? [root@ovirt-1 ~]# hosted-engine --vm-status The hosted engine configuration has not been retrieved from shared storage. Please ensure that ovirt-ha-agent is running and the storage server is reachable. [root@ovirt-2 ~]# hosted-engine --vm-status !! Cluster is in GLOBAL MAINTENANCE mode !! --== Host ovirt-3.xxxxx.com (id: 2) status ==-- Host ID : 2 Host timestamp : 12515451 Score : 3274 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : ovirt-3.xxxxx.com Local maintenance : False stopped : False crc32 : 9cf92792 conf_on_shared_storage : True local_conf_timestamp : 12515451 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=12515451 (Mon Apr 25 14:08:51 2022) host-id=2 score=3274 vm_conf_refresh_time=12515451 (Mon Apr 25 14:08:51 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host ovirt-2.xxxxx.com (id: 3) status ==-- Host ID : 3 Host timestamp : 12513269 Score : 3400 Engine status : {"vm": "up", "health": "good", "detail": "Up"} Hostname : ovirt-2.xxxxx.com Local maintenance : False stopped : False crc32 : 4a89d706 conf_on_shared_storage : True local_conf_timestamp : 12513269 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=12513269 (Mon Apr 25 14:09:00 2022) host-id=3 score=3400 vm_conf_refresh_time=12513269 (Mon Apr 25 14:09:00 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False !! Cluster is in GLOBAL MAINTENANCE mode !! [root@ovirt-3 ~]# hosted-engine --vm-status !! Cluster is in GLOBAL MAINTENANCE mode !! --== Host ovirt-1.xxxxx.com (id: 1) status ==-- Host ID : 1 Host timestamp : 6750990 Score : 0 Engine status : unknown stale-data Hostname : ovirt-1.xxxxx.com Local maintenance : False stopped : True crc32 : 5290657b conf_on_shared_storage : True local_conf_timestamp : 6750950 Status up-to-date : False Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=6750990 (Thu Feb 17 22:17:53 2022) host-id=1 score=0 vm_conf_refresh_time=6750950 (Thu Feb 17 22:17:12 2022) conf_on_shared_storage=True maintenance=False state=AgentStopped stopped=True --== Host ovirt-3.xxxxx.com (id: 2) status ==-- Host ID : 2 Host timestamp : 12515501 Score : 3279 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : ovirt-3.xxxxx.com Local maintenance : False stopped : False crc32 : 0845cd93 conf_on_shared_storage : True local_conf_timestamp : 12515501 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=12515501 (Mon Apr 25 14:09:42 2022) host-id=2 score=3279 vm_conf_refresh_time=12515501 (Mon Apr 25 14:09:42 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host ovirt-2.xxxxx.com (id: 3) status ==-- Host ID : 3 Host timestamp : 12513309 Score : 3400 Engine status : {"vm": "up", "health": "good", "detail": "Up"} Hostname : ovirt-2.xxxxx.com Local maintenance : False stopped : False crc32 : 237726e0 conf_on_shared_storage : True local_conf_timestamp : 12513309 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=12513309 (Mon Apr 25 14:09:39 2022) host-id=3 score=3400 vm_conf_refresh_time=12513309 (Mon Apr 25 14:09:39 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False !! Cluster is in GLOBAL MAINTENANCE mode !!

2 18

Self-hosted engine 4.5.0 deployment fails
by Mohamed Roushdy 03 May '22

03 May '22

Hello, I’m deploying on Ovirt nodes v4.5.0.1, but it fails to deploy the self-hosted engine with the following errors in the web installer: [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page is up] [ ERROR ] fatal: [localhost -> 192.168.222.197]: FAILED! => {"attempts": 30, "changed": false, "connection": "close", "content_encoding": "identity", "content_length": "86", "content_type": "text/html; charset=UTF-8", "date": "Tue, 03 May 2022 15:57:20 GMT", "elapsed": 0, "msg": "Status code was 500 and not [200]: HTTP Error 500: Internal Server Error", "redirected": false, "server": "Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1", "status": 500, "url": http://localhost/ovirt-engine/services/health} [ INFO ] TASK [ovirt.ovirt.engine_setup : Clean temporary files] [ INFO ] changed: [localhost -> 192.168.222.197] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost -> 192.168.222.197] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Change ownership of copied engine logs] [ INFO ] changed: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} Any idea if this is a bug or something? I tried to deploy for eight times with different configuration Thank y9ou,

1 0