VM remote console issue related to VNC and Root CA certs?

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
participants (1)
-
Chris Smith