[rhos-list] Nova-network woes (Vnc issue now)

Russell Bryant rbryant at redhat.com
Fri Mar 22 17:06:17 UTC 2013


On 03/22/2013 11:48 AM, Kashif Mohammad wrote:
> Hi Russell
> 
>>> does the browser fail to connect to anything at all?
> 
> Yes, it fails to connect to anything at all. It fails with this error
> 
> Failed to connect to server (code: 1006)

Actually, it is connecting to the VNC proxy.  That's what I was trying
to get at.  That message is inside of the novnc HTML5 vnc viewer.  So
the VNC proxy is failing to make a VNC connection to your instance.

> I can get a token through get-vnc-console. What I understand that request is coming on public address on controller node and vnc is running on private address on a different compute node.  Does nova suppose to add a route for this? Looking at route table

Your browser connects to the VNC proxy successfully via the public IP
address.  The proxy should then connect to the VNC server for the
instance.  The address used to connect to the VNC server internally to
nova is from the vncserver_proxyclient_address option, which you have
set to 192.168.9.3 on your compute node.

Check to see if the VNC connection is getting blocked by iptables on
your compute node.

-- 
Russell Bryant




More information about the rhos-list mailing list