September 2022 - Users - oVirt List Archives

vdsm.log full of "error" because node don't run the "engine"
by Diego Ercolani 12 Sep '22

12 Sep '22

Hello, I don't know if it's normal but in all the nodes of the cluster (except the one that runs the engine) I have something like: 2022-09-12 15:41:54,563+0000 INFO (jsonrpc/0) [api.virt] START getStats() from=::1,57578, vmId=8486ed73-df34-4c58-bfdc-7025dec63b7f (api:48) 2022-09-12 15:41:54,563+0000 INFO (jsonrpc/0) [api] FINISH getStats error=Virtual machine does not exist: {'vmId': '8486ed73-df34-4c58-bfdc-7025dec63b7f'} (api:129) 2022-09-12 15:41:54,563+0000 INFO (jsonrpc/0) [api.virt] FINISH getStats return={'status': {'code': 1, 'message': "Virtual machine does not exist: {'vmId': '8486ed73-df34-4c58-bfdc-7025dec63b7f'}"}} from=::1,57578, vmId=8486ed73-df34-4c58-bfdc-7025dec63b7f (api:54) 2022-09-12 15:41:54,563+0000 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call VM.getStats failed (error 1) in 0.00 seconds (__init__:312) The UUID 8486ed73-df34-4c58-bfdc-7025dec63b7f is the UUID of the Hosted-engine VM, obviously it run only in one noe and, as I undestand, the other nodes are querying the VM state only to fence the VMs if is started on more node at a time... but having the log full of these "error" are annoying. I would prefer to have the word "error" only in meaningful context. This if the hypotesis of my interpretation is correct, if it's a true error, then please address me how to fix it. Thank you.

1 0

vm migration failed with certifacate issue
by parallax 11 Sep '22

11 Sep '22

ovirt 4.4.4.7 not able to migrate VMs between hosts with following vdsm error: operation failed: Failed to connect to remote libvirt URI qemu+tls://kvm4.imp.loc/system: authentication failed: Failed to verify peer's certificate hosts certificates was renewed recently but hosts hasn't been reloaded how to fix this issue

2 2

remote-viewer "Change CD menu" contains ISOs only from one storage domain
by Alexander Murashkin 09 Sep '22

09 Sep '22

remote-viewer "Change CD menu" contains ISOs only from one storage domain. There are two "data" storage domains in the datacenter. Both of them contains ISOs and VM disk images. The first VM has a disk image in the first storage domain and so is shown in the domain's "Virtual Machine" tab. Similar, the second VM has a disk image in the second storage domain and so is also shown in the domain's "Virtual Machine" tab. When the VMs are running, in their consoles, in "Change CD menu" only ISOs from the first storage domain are listed. I would consider it a bug. It is possible to attach ISO from any storage domain to any VM. But it is not possible to see ISO from the second domain in "Change CD menu". Engine RPM: ovirt-engine-4.5.2.5-1.el8.noarch. Desktop RPMs: libgovirt-0.3.8-3.fc36.x86_64 virt-viewer-11.0-2.fc36.x86_64 Shall I open a bug in Bugzilla? If so, what component it is related to - libgovirt? Alexander Murashkin PS I also have tried ISO domain. No luck.

1 0

VM remote console issue related to VNC and Root CA certs?
by Chris Smith 09 Sep '22

09 Sep '22

Hello, I have built a small 2 cluster "datacenter". One host is oVirt 4.5.1 and another 4.5.2. Each host is in it's own cluster due to CPU type difference. I am able to build VMs on each host and they are able to start. My issue I am fighting now is that I am unable to get remote-viewer.exe to open a remote console window to a VM on the 2nd cluster I've built. I'm trying to connect to a VM named "utm" which is running on host "mini-node" which is in a separate cluster from where "ovirt-node" resides. "ovirt-node" is the host where "ovirt-engine" resides. I have attached the whole log to this e-mail from my windows machine, and I think this part is most relevant: [image: image.png] I've tried to install the SSL certs for each server (from tcp/9090) on my windows workstation's cert store in both user and computer personal and trusted root ca store, but i'm not sure that the cert I have for my 2nd host is made right? [image: image.png] [image: image.png] This is my ovirt engine cert (ignore the comcast.net domain name, that is due to linksys nonsense that i'm just running with): [image: image.png] [image: image.png] I wonder, should SSL cert for "mini-node" have been issued by "ovirt-engine"? i think it's self-signed at the moment. Here is what my console.vv looks like: [virt-viewer] type=vnc host=mini-node.hsd1.fl.comcast.net port=5900 password=<snip> # Password is valid for 120 seconds. delete-this-file=1 fullscreen=0 title=utm:%d toggle-fullscreen=shift+f11 release-cursor=shift+f12 secure-attention=ctrl+alt+end versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6;rhel6:99.0-1 newer-version-url= http://www.ovirt.org/documentation/admin-guide/virt/console-client-resources [ovirt] host=ovirt-engine.hsd1.fl.comcast.net:443 vm-guid=cdfe33fc-4d6e-425d-b5d2-d999f56ea4ea sso-token=<snip> admin=1 ca=-----BEGIN CERTIFICATE----- <snip> Any help is appreciated, Thank you, Chris

1 0

Cannot upgrade hosted-engine due to a LUN in a storage domain
by virden-gerald＠aramark.com 09 Sep '22

09 Sep '22

I need to know if there are any cli commands to manage storage domains. I have a completely empty LUN in a storage domain but I can't use it to apply to my hosted-engine upgrade. I think I need to put the storage domain into maintenance mode and remove it but I don't have the GUI to do this. Anyone know how to use the command line for this?

1 0

hosted-engine -vm-status show a ghost node that is not anymore in the cluster: how to remove?
by Diego Ercolani 08 Sep '22

08 Sep '22

engine 4.5.2.4 The issue is that in my cluster when I use the: [root@ovirt-node3 ~]# hosted-engine --vm-status --== Host ovirt-node3.ovirt (id: 1) status ==-- Host ID : 1 Host timestamp : 1633143 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : ovirt-node3.ovirt Local maintenance : False stopped : False crc32 : 1cbfcd19 conf_on_shared_storage : True local_conf_timestamp : 1633143 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=1633143 (Wed Aug 31 14:37:53 2022) host-id=1 score=3400 vm_conf_refresh_time=1633143 (Wed Aug 31 14:37:53 2022) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False --== Host ovirt-node1.ovirt (id: 2) status ==-- Host ID : 2 Host timestamp : 373629 Score : 0 Engine status : unknown stale-data Hostname : ovirt-node1.ovirt Local maintenance : True stopped : False crc32 : 12a6eb81 conf_on_shared_storage : True local_conf_timestamp : 373630 Status up-to-date : False Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=373629 (Tue Jun 14 16:48:50 2022) host-id=2 score=0 vm_conf_refresh_time=373630 (Tue Jun 14 16:48:50 2022) conf_on_shared_storage=True maintenance=True state=LocalMaintenance stopped=False --== Host ovirt-node2.ovirt (id: 3) status ==-- Host ID : 3 Host timestamp : 434247 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : ovirt-node2.ovirt Local maintenance : False stopped : False crc32 : badb3751 conf_on_shared_storage : True local_conf_timestamp : 434247 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=434247 (Wed Aug 31 14:37:45 2022) host-id=3 score=3400 vm_conf_refresh_time=434247 (Wed Aug 31 14:37:45 2022) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False --== Host ovirt-node4.ovirt (id: 4) status ==-- Host ID : 4 Host timestamp : 1646655 Score : 3400 Engine status : {"vm": "up", "health": "good", "detail": "Up"} Hostname : ovirt-node4.ovirt Local maintenance : False stopped : False crc32 : 1a16027e conf_on_shared_storage : True local_conf_timestamp : 1646655 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=1646655 (Wed Aug 31 14:37:43 2022) host-id=4 score=3400 vm_conf_refresh_time=1646655 (Wed Aug 31 14:37:43 2022) conf_on_shared_storage=True maintenance=False state=EngineUp stopped=False The problem is that ovirt-node1.ovirt is not anymore in ther cluster, in the host list presented by the ui there is correctly no ovirt-node1, the ovirt-node1 appears only in the commandline. I did a full text search in the engine DB, but node1 doesn't appear anywhere, even in the filesystem, a grep doesn't find anything

2 5

Ovirt Windows VM Provisioning with Terraform and Sysprep
by venkatar＠emiratesnbd.com 08 Sep '22

08 Sep '22

Hi All, Did anyone tried automated deployment of windows VM in ovirt using terraform ovirt provider (https://github.com/oVirt/terraform-provider-ovirt) We are able to provision the Linux VM, want to check if anyone tried windows VM. I have sample sysprep script which will assign IP,Set hostname and password. I couldn't find anything related over internet for the same. Thanks Ravi

1 0

Engine and host certificates expired
by simon＠justconnect.ie 08 Sep '22

08 Sep '22

I have an environment where the engine wouldn’t start and the certificate expiry dates were as follows. Host1 - 25th Sep 2022 Host2 - 11th Aug 2022 Host3 - 11th Aug 2022 I copied the vdsm certs from Host1 to Host2 & Host3 Engine then started on Host1 and then backed up. Engine cert expiry 11th Aug 2022 I put the cluster into Global Maintenance mode and then tried: ‘engine-setup —offline’ Which failed as the validation check said the engine wasn’t in Global Maintenance mode even though ‘hosted-engine —vm-status said it was. None of the Hosts are ‘GREEN’ (can’t remember what the status was as I’m writing this from memory) but their status is ’RED’. There are VMs running on the 3 Hosts and I’m reluctant to restart anything at the moment. Is there a way to refresh the engine certificate to get past this or do I need to restart vdsm service on each host to bring them back online as far as the engine is concerned? The environment is currently at 4.4.6 and is to be upgraded to 4.5.2 next month. Any help as always will be greatly appreciated. Kind regards Simon

3 9

oVirt 4.5.2.4 api access with keycloak
by Don Dupuis 07 Sep '22

07 Sep '22

Hello I have installed ovirt 4.5.2.4 and keycloak authentication is now standard. On previous installs it could be accessed via a web browser as https://engine_FQDN/ovirt-engine/api. What is the proper url syntax to work with the new keycloak way and I know the username is now admin@ovirt @internalsso? Thanks Don

4 3

VDSNetworkException: protocol version not accepted by client
by Kilian Ries 07 Sep '22

07 Sep '22

Hi, im running an oVirt 4.2.8 cluster with two nodes. A few days ago, my SSL certificates expired. After that, i changed all the certificates on the engine via "engine-upgrade" command and issued new vdsm client certificates. Then i copied the new certificates to my ovirt nodes and restarted vdsmd (systemctl restart vdsmd). Now i'm still not able to connect to my ovirt nodes. In the engine log i can see the following error: ### 2022-09-01 18:25:51,822+02 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connecting to /192.168.xx.xx 2022-09-01 18:25:51,827+02 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages The server selected protocol version TLS10 is not accepted by client preferences [TLS12] 2022-09-01 18:25:51,829+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-88) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: The server selected protocol version TLS10 is not accepted by client preferences [TLS12] ### I searched my vdsm client config but i cannot see any specific TLS version set (every option with TLS is commented - seems to be the default): ### $grep -R -i TLS /etc/vdsm/ /etc/vdsm/vdsm.conf:# ssl_protocol = tlsv1 /etc/vdsm/vdsm.conf:# https://docs.python.org/2/library/ssl.html. e.g. OP_NO_TLSv1, /etc/vdsm/vdsm.conf:# OP_NO_TLSv1_1 By default tlv1, tlsv1.1 and tlsv1.2 are enabled. ### On the engine i didn't find any setting to set a specific TLS version - there seems to have been a setting (VdsmSSLProtocol) but that got deprecated years ago. Does anybody know why my engine is still not able to connect to the client vdsmd? I also tried to set "ssl_protocol = tlsv1" via vdsm.conf but that didn't work ... Thanks Regards, Kilian PS: Name : vdsm Architektur : x86_64 Version : 4.19.37 Ausgabe : 1.el7.centos Name : ovirt-engine Architektur : noarch Version : 4.2.8.2 Ausgabe : 1.el7

2 2