Bug 1044464

Summary: [RHEV] [spice]: Unable to connect to the graphic server
Product: Red Hat Enterprise Virtualization Manager Reporter: iakov Gan <iakov.gan>
Component: ovirt-engine-webadmin-portalAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED CANTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, ecohen, gklein, iakov.gan, iheim, juan.hernandez, michal.skrivanek, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-13 07:13:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description iakov Gan 2013-12-18 11:09:34 UTC
This bug is related to RHEV not to oVirt. Unfortunately i can not find relevant product in bugzilla.  

Description of problem:
Unable to connect to console of a RHEV VM. 

Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version : 3.2.4-0.44.el6ev

How reproducible:
whenever i try to open console of a VM, i get a message "unable to connect to the graphic server"  

Steps to Reproduce:
1. open RHEV 
2. Choose a VM and click a console button in the toolbar


Actual results: Black window with a message 
Expected results: Console 

Additional info:
I followed this solution https://access.redhat.com/site/solutions/348793, and i installed 2 packages mentioned there. Did not worked for me so far.

Comment 1 Itamar Heim 2014-01-12 08:43:11 UTC
setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.

Comment 3 Juan Hernández 2014-01-18 14:54:30 UTC
I think that this isn't related to the API, so we will probably have to change the component of the bug.

But you can use the API to gather information that will allow you to do some diagnostics. Go the the API resource for this VM:

  https://your.engine.host/api/vms/the_id_of_the_vm

There you will get a XML description of the VM, including the display characteristics:

  <vm id="..." href="...">
    ...
    <display>
      <type>spice</type>
      <address>192.168.122.20</address>
      <port>5900</port>
      <secure_port>5901</secure_port>
      ...
    </display>
  </vm>

You can use the IP address and the secure port properties to check if you can establish a TCP connection from your client machine. Try to ping that IP address from your client machine, and if your client is a Linux machine try to use the openssl command to connect to the secure port:

  # openssl s_client -connect 192.168.122.20:5901

In a working installation this should print the details of the SSL connection, something starting like this:

  CONNECTED(00000003)
  depth=1 C = US, O = Example Inc., CN = rhel.example.com.29553
  verify error:num=19:self signed certificate in certificate chain
  verify return:0

If there is no connectivity, or if the secure port is blocked by a firewall, you will instead see something like this:

  socket: Connection refused
  connect:errno=111

Or the command to connect may just take a few minutes to complete and you will see something like this:

  socket: Connection timed out
  connect:errno=110

If you see any of these failures then you have an IP connectivity problem between your client and the hypervisor where the VM is running. You will have to fix this connectivity problem.

Comment 4 Michal Skrivanek 2014-01-22 13:23:24 UTC
(In reply to iakov Gan from comment #0)

for future reference the right product is "Red Hat Enterprise Virtualization Manager"

Comment 5 Michal Skrivanek 2014-01-27 09:00:51 UTC
How are you opening your console? (browser plugin / .vv file download and remote-viewer file type association / browser client noVNC&spice_html5)

Are you using 3rd party SSL certificate or engine issued? Did you import it into the browser?

Comment 6 iakov Gan 2015-08-24 12:22:57 UTC
Please close. We dropped RHEV.