May 2022 - Users - Ovirt List Archives

i need change legacy to ovs switch mode on oVirt node's

by sultanu＠inbox.ru

Hello, Team! I need help. I have cluster with 3 nodes oVirt 4.4.10 and common ISCSI storage, i have hosted engine installed on it. I wont change legacy to ovs switch mode, using instruction below: - Install first host and VM using "hosted-engine --deploy" - In the Engine UI, change Cluster switch type from Legacy to OVS - Shutdown the engine VM and stop vdsmd on the host. - Manually change the switch type to ovs in /var/lib/vdsm/persistence/netconf/nets/ovirtmgmt - Restart the host After this changing my hosted engine don't wont start, it says i have a problem with vnet interface, i don't know virtmanager or i don't know vnetuser. When i had return back settings from ovs to legacy mode, hosted engine start without any problem When i had change file /var/lib/vdsm/persistence/netconf/nets/ovirtmgmt on hosts without hosted engine, they are change network mode and start working as ovs switch mode but they say network out of sync. I tryed to migrate hosted engine from host with legacy switch to host with ovs switch hosted engine don't wont migrate. Could you help me please.

2 years, 8 months

2
1
0 / 0

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

by Liebe, André-Sebastian

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

2 years, 8 months

2
1
0 / 0

Ovirt engine Isuue

by sachendra.shukla＠yagnaiq.com

We have installed ovirt engine on centos 8 by follow the below commond nano /etc/hosts your-server-ip centos.example.com dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm dnf module enable javapackages-tools -y dnf module enable pki-deps -y dnf module enable postgresql:12 -y dnf update -y dnf install ovirt-engine -y engine-setup (when we require latest version setsebool -P httpd_can_network_connect 1 firewall-cmd --permanent --zone public --add-port 80/tcp firewall-cmd --permanent --zone public --add-port 443/tcp firewall-cmd --reload But we are unable to connect by browser shwing below error. 500 - Internal Server Error

2 years, 8 months

3
3
0 / 0

Re: Getting error on oVirt installation

by Kevin Cahill

I am also struggling with this as I try to install a self-hosted engine. I have read every thread in the forum and tried all the suggestions. Here is my most recent attempt (RHEL 8.5, installing oVirt 4.4): Start the hosted engine deployment, then run the command [ # dnf downgrade postgresql-jdbc ] from a virsh console, to downgrade postgresql as soon as the packages are done updating. The downgrade appears to be successful, however the system still fails at 'Check if engine health page is up'. Restarting the oVirt engine [ # systemctl restart oVirt-engine ] immediately after downgrading postgresql does not make any difference. The system times out at the 'Check if engine health page is up'. The log entry where the latest failure started to occur is below. I can include the entire log if needed. Interestingly, the status was 503 this time. In many prior attempts that status was 500. 2022-05-06 09:42:49,744-0400 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:110 fatal: [localhost -> 192.168.222.150]: FAILED! => {"attempts": 30, "changed": false, "connection": "close", "content": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>503 Service Unavailable</title>\n</head><body>\n<h1>Service Unavailable</h1>\n<p>The server is temporarily unable to service your\nrequest due to maintenance downtime or capacity\nproblems. Please try again later.</p>\n</body></html>\n", "content_length": "299", "content_type": "text/html; charset=iso-8859-1", "date": "Fri, 06 May 2022 13:42:49 GMT", "elapsed": 0, "msg": "Status code was 503 and not [200]: HTTP Error 503: Service Unavailable", "redirected": false, "server": "Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1 mod_wsgi/4.6.4 Python/3.6", "status": 503, "url": http://localhost/ovirt-engine/services/health} I would like to know if anyone has had success doing a fresh install of a self-hosted environment since the postgresql issue arose. If so, any pointers would be greatly appreciated. If I get this working I will follow up with exactly what I did.

2 years, 8 months

1
0
0 / 0

Set password for VM

by vysikantsev＠gmail.com

How to set password for Virtual machine?

2 years, 8 months

2
1
0 / 0

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

2 years, 8 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

2 years, 8 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

2 years, 8 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

2 years, 8 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

2 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users May 2022