[Yahoo-eng-team] [Bug 1260118] Re: VNC on compute node refused connection from controller
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: " Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON). Valid example: CONFIRMED FOR: LIBERTY ** Changed in: nova Importance: Low => Undecided ** Changed in: nova Status: Confirmed => Expired -- 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): Expired 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1260118] Re: VNC on compute node refused connection from controller
** Also affects: nova Importance: Undecided Status: New -- 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): New 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
