May 2022 - Users - Ovirt List Archives

HELP ME! Failed to validate the SSL certificate for localhost:443

by natchawi28＠gmail.com

Hi, I'm having an issue with Failed to validate the SSL certificate for localhost:443 during Deploy "hosted-engine." check the log files, found this error: " [TASK] [ovirt.engine-setup: Check if Engine health page is up] [ERROR] fatal:[localhost -> my_fqdn.domain]:FAILED!=>{"attempts":12, "changed":false,"msg":"Failed to validate the SSL certificate for localhost:443. Make sure your managed systems have a valid CA certificate installed. You can use validate_certs=False if you do not need to confirm the servers identity but this is unsafe and not recommended. Paths checked for this patform: /etc/ssl/certs, /etc/pki/ca-trust/extracted/pem, /etc/pki/tls/certs, /usr/share/ca-certificates/cacert.org, /etc/ansible. The exception msg was: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618).", "status": -1, "url": "http://localhost/ovirt-engine/services/health"} " NOTE: ovirt engine VERSION "ovirt-engine-appliance-4.3-20200603.1.0.2.el7.x86_64" We tried googling to resolve this issue but, unfortunately, unsuccessfully. Can someone help us to solve our critical issue? Best regards, Bunnatee

1 year, 11 months

4
10
0 / 0

Getting error on oVirt installation

by mahmutduzenn＠gmail.com

Hello, I downloaded the oVirt node and installed it on my server. DNS etc. I made the settings. I'm getting an error in the Hosted engine installation step. The error message I got is as follows: [ INFO ] TASK [ovirt.ovirt.engine_setup : Run engine-config] [ INFO ] TASK [ovirt.ovirt.engine_setup : Restart engine after engine-config] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page is up] [ ERROR ] fatal: [localhost -> 192.168.2.94]: FAILED! => {"attempts": 30, "changed": false, "connection": "close", "content_encoding": "identity", "content_length": "86", "content_type": "text/html; charset= UTF-8", "date": "Fri, 29 Apr 2022 02:52:21 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.2.94] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost -> 192.168.2.94] [ 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"} How can I fix this. thanks

1 year, 11 months

5
8
1 / 0

Lockspace volume not recognized after NFS outage

by joustie＠gmail.com

Hi, I am running a 3 node Ovirt cluster with a hosted-engine. Unfortunately I had a small issue on my NFS server which provides the shared storage for the cluster. During the outage, all VM's went into pause, and the cluster itself (hosted engine) went down. After restoring nfs service (took 2 minutes), the cluster did not recover. The HA agent can't make sense of the lockspace anymore it seems. The agent fails on all nodes. There are several errors in logs but the main one is (I think) in broker.log: MainThread::WARNING::2022-05-01 22:06:06,085::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: Command Image.prepare with args {'imageID': 'c1b7e131-bbde-416b-b2a0-de746a039dfd', 'storagepoolID': '00000000-0000-0000-0000-000000000000', 'volumeID': 'b221ea37-2c59-49bf-89f7-83766fb53717', 'storagedomainID': 'e3b467ec-fdfc-4c7a-9725-8a6d1fe18c6d'} failed: (code=201, message=Volume does not exist: (u'b221ea37-2c59-49bf-89f7-83766fb53717',)) Which is weird because it seems to exist: ls -l /rhev/data-center/mnt/nas.fritz.box:_mnt_HD_HD__a2_hosted__engine__nas/e3b467ec-fdfc-4c7a-9725-8a6d1fe18c6d/images/c1b7e131-bbde-416b-b2a0-de746a039dfd total 1049608 -rw-rw----. 1 vdsm kvm 1073741824 May 1 15:35 b221ea37-2c59-49bf-89f7-83766fb53717 -rw-rw----. 1 vdsm kvm 1048576 Dec 21 2020 b221ea37-2c59-49bf-89f7-83766fb53717.lease -rw-rw-rw-. 1 vdsm kvm 329 Dec 21 2020 b221ea37-2c59-49bf-89f7-83766fb53717.meta When I try to reinitialize the lockspace (stopping the agent etc) I get: ---- File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 60, in connect self.sock.connect(base64.b16decode(self.host)) File "/usr/lib64/python2.7/socket.py", line 224, in meth return getattr(self._sock,name)(*args) socket.error: [Errno 2] No such file or directory Is there a way to to this manually and also recreate the lockspace volume? I already tried to recreate the lockspace manually with: sanlock direct init -s hosted-engine:0:/rhev/data-center/mnt/nas.fritz.box:_mnt_HD_HD__a2_hosted__engine__nas/e3b467ec-fdfc-4c7a-9725-8a6d1fe18c6d/ha_agent/hosted-engine.lockspace:0 which resulted in: init done -19 No further info and nothing changed. With kind regards, Joost

1 year, 11 months

2
1
0 / 0

OVS switch type for hosted-engine

by Devin A. Bougie

Is it possible to setup a hosted engine using the OVS switch type instead of Legacy? If it's not possible to start out as OVS, instructions for switching from Legacy to OVS after the fact would be greatly appreciated. Many thanks, Devin

1 year, 11 months

4
5
2 / 0

Re: could not start ovirt-engine: TagsDirector.init() fails

by Liebe, André-Sebastian

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/FA6BLIAIYY7G...) 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 year, 11 months

1
0
0 / 0

Virt group has no storage.owner-uid/gid anymore

by Strahil Nikolov

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 year, 11 months

1
0
0 / 0

Re: [IMPORTANT] Upgrade to postgresql-jdbc-42.2.14-1 breaks oVirt Engine 4.4/4.5

by laj811＠gmail.com

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 year, 11 months

1
0
0 / 0

ovirt engine restore: Failed to construct component instance

by Rafhael Almeida

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 !!

1 year, 11 months

2
2
1 / 0

Re: Ovirt 4.5.0.1 self-hosted deployment fails - jboss errors

by hans＠jiflin.nl

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,

1 year, 11 months

2
1
0 / 0

Async release for ovirt-engine (4.5.0.6) is now available

by Lev Veyde

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 year, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users May 2022