- Users - oVirt List Archives

certification expires: PKIX path validation failed
by Nathanaël Blanchet 13 Apr '22

13 Apr '22

Hi, Some of my hosts came into a non responsive state since there certicate had expired: VDSM palomo command Get Host Capabilities failed: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed |openssl x509 -noout -enddate -in /etc/pki/vdsm/certs/vdsmcert.pem palomo notAfter=Apr 6 11:09:05 2022 GMT | The recommanded path to update certificates is to put hosts into maintenance and enroll certificates. But I can't anymore live migrate vms since the certificate is expired: 2022-04-13 10:34:12,022+0200 ERROR (migsrc/bf0f7628) [virt.vm] (vmId='bf0f7628-d70b-47a4-8569-5430e178f429') [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897) (migration:331) So is there a way to disable tls to migrate these vms so as to put the host into maintenance? No possibility of migration would imply to stop production vms, this is what we absolutely don't want! Any help much appreciated. || -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 2

vdsm hook after node upgrade
by Nathanaël Blanchet 13 Apr '22

13 Apr '22

Hi, I've upgraded my hosts from 4.4.9 to 4.4.10 and none of my vdsm hooks are present anymore... i believed those additionnal personnal data were persistent across update... -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

4 7

ovirt-dr generate
by Colin Coe 12 Apr '22

12 Apr '22

Hi all I'm trying to run ovirt-dr generate but its failing: /usr/share/ansible/collections/ansible_collections/redhat/rhv/roles/disaster_recovery/files/ovirt-dr generate Log file: '/tmp/ovirt-dr-1649673243333.log' [Generate Mapping File] Connection to setup has failed. Please check your credentials: URL: https://server.fqdn/ovirt-engine/api user: admin@internal CA file: ./ca.pem [Generate Mapping File] Failed to generate var file. When I examine the log file: 2022-04-11 18:34:03,332 INFO Start generate variable mapping file for oVirt ansible disaster recovery 2022-04-11 18:34:03,333 INFO Site address: https://server.fqdn/ovirt-engine/api username: admin@internal password: ******* ca file location: ./ca.pem output file location: ./disaster_recovery_vars.yml ansible play location: ./dr_play.yml 2022-04-11 18:34:03,343 ERROR Connection to setup has failed. Please check your credentials: URL: https://server.fqdn/ovirt-engine/api user: admin@internal CA file: ./ca.pem 2022-04-11 18:34:03,343 ERROR Error: Error while sending HTTP request: (60, 'SSL certificate problem: unable to get local issuer certificate') 2022-04-11 18:34:03,343 ERROR Failed to generate var file. My suspicion is that the script doesn't like third party certs. Has anyone got this working with third party certs? If so, what did you need to do? Thanks

4 4

Couldn't connect to VDSM within 60 seconds
by pasquale.borrelli＠synlab.it 11 Apr '22

11 Apr '22

Hi, we have 3 hosts and a self-hosted engine VM (ovirt version 4.4.). After rebooting all the hosts, we are unable to start the VM hosted-engine. In particular, the output of 'hosted-engine --vm-start' is as follows: "The hosted engine configuration has not been retrieved from shared storage yet, for more details please check sanlock status." We checked the sanlock, ovirt-ha-agent and broker status but all are "active (running)". Checking the log files, all share the common error "RuntimeError: Couldn't connect to VDSM within 60 second", returned in loop. In the vdsm.log we found this error: " 2022-04-05 16:20:11,786+0200 INFO (periodic/0) [vdsm.api] START repoStats(domains=()) from=internal, task_id=8541000f-e7fd-4b59-8ae6-522c87538688 (api:48) 2022-04-05 16:20:11,786+0200 INFO (periodic/0) [vdsm.api] FINISH repoStats return={} from=internal, task_id=8541000f-e7fd-4b59-8ae6-522c87538688 (api:54) 2022-04-05 16:20:11,789+0200 WARN (periodic/0) [root] Failed to retrieve Hosted Engine HA info, is Hosted Engine setup finished? (api:168) " We tried googling to resolve this issue but, unfortunately, unsuccessfully. Can someone help us to solve our critical issue? Bests, Pasquale

4 9

Recall: Ovirt 4.4.10 lab unstable on ESXi
by Mohamed Roushdy 11 Apr '22

11 Apr '22

Mohamed Roushdy would like to recall the message, "Ovirt 4.4.10 lab unstable on ESXi".

1 0

Ovirt 4.4.10 lab unstable on ESXi
by Mohamed Roushdy 11 Apr '22

11 Apr '22

Hello, I’m used to having a nested-ESXi on another ESXi, but we are testing Ovirt these days, and we are facing a strange behavior with the engine VM. I have a hyper-converged Ovirt cluster with a hosted-engine, and whenever I reboot/shutdown one of the nodes for testing (a node that is not hosting the engine VM of course) the engine goes crazy and too slow, and starts losing network connecting to the remaining (healthy) nodes in the cluster, and I can hardly SSH into it. Ping also has too many drops while another node is down. Once that faulty node is up again the engine works very fine, but this is really limiting my ability to make further Ovirt HA tests before moving to production. I though maybe the promiscuous mode on the physical host causes this, but never faced this with nester-virtualization with VMware, and turning-off promiscuous mode isn’t an option either… what do you think please? Mohamed Roushdy Team Member – Systems Administrator M: +31 61 55 94 300 [signature_514057058]<https://peopleintouch.com/>[signature_1294661742]<https://www.linkedin.com/authwall?trk=bf&trkInfo=AQGK3xaGp-v5DAAAAX16b8yY54…>

1 0

Ovirt 4.4 - (Restore from 4.3): The provided authorization grant for the auth code has expired. (all Users)
by fabian.mohren＠qbeyond.de 11 Apr '22

11 Apr '22

Hi, we install ovirt 4.4 on a fresh Redhat 8.5 Installation. Next Restore the oVirt Backup (https://www.ovirt.org/documentation/upgrade_guide/#Remote_Upgrading_from_4-3) We use a external Certificate.I copy all certs/key from old installation to the new Manager. No matter with which user I log in - the same error message always appears. Also create a new user - had no success. Same error message Unfortunately there is nothing new in the logfile - except exactly this message. Setting the log level to "DEBUG" for all services did not bring any new or clearer error messages. The time is set correctly - this can almost not be the cause. Unfortunately I have no idea what the cause is and how I can solve this - I hope you have another idea. Thanks & many greetings

4 8

VM failed to start when host's network is down
by lizhijian＠fujitsu.com 08 Apr '22

08 Apr '22

Post again after subscribing the mail list. Hi guys I have an all in one ovirt environment which node installed both vdsm and ovirt-engine. I have setup the ovirt environment and it could work well. For some reasons, i have to use this ovirt with node's networking down(i unplugged the network cable) In such case, I noticed that i cannot start a VM anymore. I wonder if there is a configuration switch to enable a ovirt to work with node's networking down ? if not, may i possible to make it work by a easy way ? When i tried to start VM with ovirt API, it responses with: ```bash [root@74d2ab9cb0 ~]# sh start.sh <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <action> <async>false</async> <fault> <detail>[Cannot run VM. Unknown Data Center status.]</detail> <reason>Operation Failed</reason> </fault> <status>failed</status> </action> [root@74d2ab9cb0 ~]# sh start.sh <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <action> <async>false</async> <fault> <detail>[Cannot run VM. Unknown Data Center status.]</detail> <reason>Operation Failed</reason> </fault> <status>failed</status> </action> [root@74d2ab9cb0 ~]# ``` Attached the vdsm and ovirt-engine Thanks Zhijian

2 1

Wait for the engine to come up on the target vm
by Vladimir Belov 08 Apr '22

08 Apr '22

I'm trying to deploy oVirt from a self-hosted engine, but at the last step I get an engine startup error. [ INFO ] TASK [Wait for the engine to come up on the target VM] [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": true, "cmd": ["hosted-engine", "--vm-status", "--json"], "delta": "0:00:00.181846", "end": "2022-03-28 15:41:28.853150", "rc": 0, "start": "2022-03-28 15:41:28.671304", "stderr": "", "stderr_lines": [], "stdout": "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\": \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537 (Mon Mar 28 15:41:20 2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", \"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": false, \"maintenance\": false, \"crc32\": \"4d2eeaea\", \"local_conf_timestamp\": 5537, \"host-ts\": 5537}, \"global_maintenance\": false}", "stdout_lines": ["{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\": \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537 (Mon Mar 28 15:41:20 2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", \"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": false, \"maintenance\": false, \"crc32\": \"4d2eeaea\", \"local_conf_timestamp\": 5537, \"host-ts\": 5537}, \"global_maintenance\": false}"]} Аfter the installation is completed, the condition of the engine is as follows: Engine status: {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} After reading the vdsm.logs, I found that qemu-guest-agent failed to connect to the engine for some reason. Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5400, in qemuGuestAgentShutdown self._dom.shutdownFlags(libvirt.VIR_DOMAIN_SHUTDOWN_GUEST_AGENT) File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 98, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 130, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2517, in shutdownFlags if ret == -1: raise libvirtError ('virDomainShutdownFlags() failed', dom=self) libvirtError: Guest agent is not responding: QEMU guest agent is not connected During the installation phase, qemu-guest-agent on the guest VM is running. Setting a temporary password (hosted-engine --add-console-password --password) and connecting via VNC also failed. Using "hosted-engine --console" also failed to connect The engine VM is running on this host Connected to HostedEngine domain Escaping character: ^] error: internal error: character device <null> not found The network settings are configured using static addressing, without DHCP. It seems to me that this is due to the fact that the engine receives an IP address that does not match the entry in /etc/hosts, but I do not know how to fix it. Any help is welcome, I will provide the necessary logs. Thanks

3 2

Gluster storage and TRIM VDO
by Oleh Horbachov 08 Apr '22

08 Apr '22

Hello everyone. I have a Gluster distributed replication cluster deployed. The cluster - store for ovirt. For bricks - VDO over a raw disk. When discarding via 'fstrim -av' the storage hangs for a few seconds and the connection is lost. Does anyone know the best practices for using TRIM with VDO in the context of ovirt? ovirt - v4.4.10 gluster - v8.6

2 3