yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #09505
[Bug 1260118] Re: VNC on compute node refused connection from controller
I don't think this is related to Horizon - we simply get the URL from
Nova and embed it in the page.
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1260118
Title:
VNC on compute node refused connection from controller
Status in OpenStack Dashboard (Horizon):
Invalid
Status in OpenStack Compute (Nova):
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1260118/+subscriptions
References