Hide Forgot
Description of problem: A warning "Could not set SSL credentials from '/tmp/govirt-ca-D7WSFY.crt'" occurs and cannot see the foreign menu on remote-viewer window Version-Release number of selected component (if applicable): # rpm -q libgovirt virt-viewer libgovirt-0.3.2-2.el6.x86_64 virt-viewer-2.0-14.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Make sure there is an iso domain and an ISO image in the domain on RHEVM and Prepare a guest on RHEVM. 2. Run below command to get and trust the ca.crt file. # wget http://$RHEVM_HOST_NAME/ca.crt # cat ca.crt >>/etc/pki/tls/certs/ca-bundle.crt # update-ca-trust 3. Download the console.vv file of the guest. 4. Run "remote-viewer console.vv". Actual results: (remote-viewer:6472): libsoup-WARNING **: Could not set SSL credentials from '/tmp/govirt-ca-D7WSFY.crt': Failed to open file '/tmp/govirt-ca-D7WSFY.crt': No such file or director Expected results: The "change CD" menu should be seen on remote-viewer window and can connect to the guest successfully. Additional info:
This is fixed upstream by https://git.gnome.org/browse/libgovirt/commit/?id=9f3fde7b2f40346ca8572803fe574d7de6060695 Imo we should fix this in 6.8 if possible.
There seems to have one remaining problem with --ovirt-ca-file even with this patch applied.
I reproduced this bug with packages from comment #1: 1. put ovirt and spice ca files to ca-bundle 2. updated ca trust 3. connected to rhevm3.6 (rhel7.3 guest) via console.vv file then I installed newest libgovirt-0.3.2-3 virt-viewer-2.0-17 Message is gone, but no foreign menu appears. if I connect via ovirt (remote-viewer ovirt://$username%40$domain@$rhevserver/$vm), then foreign menu is displayed. Attaching spice-debug
Created attachment 1229532 [details] REST_PROXY=debug and spice-debug
I see you tested on rhevm36.spice.brq.redhat.com , in order to get things to work on this one, I need to remove the last line in the .vv file (ca=... line in the [ovirt] section). I don't have access to a setup where REST CA is the same as SPICE CA in order to make sure this other case works too.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0587.html