VNC on compute node refused connection from controller

[Alfred Shen]

Nova-novncproxy threw this error when trying to connect to the VM's console via VNC. The root cause was found to be at the compute node (10.52.224.20) which dropped network connection on vnc-server port(s) (i.e. 5900+N) from the controller node.

 22: connecting to: 10.52.224.20:5903
 22: handler exception: [Errno 113] EHOSTUNREACH

A temp work-around is to manually open up vnc ports on compute node(s).

-A INPUT -m state --state NEW -m tcp -p tcp --dport 5900:5950 -j ACCEPT

Wondering if this could be addressed dynamically, during VM creation ideally. The issue was found with openstack-nova-compute-2013.2-2.el6 running on CentOS kernel 2.6.32-358.123.2.openstack.el6.x86_64.

[Julie Pichon (jpichon)]

I don't think this is related to Horizon - we simply get the URL from Nova and embed it in the page.

[Markus Zoeller (markus_z) (mzoeller)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY