VNC unreachable from Horizon

[Dmitry Tyzhnenko]

User can't connect to instance console via Horizon

Scenario:
1. Create new environment
2. Choose Neutron, VLAN
3. Choose Ceph for images
4. Add 3 controller
5. Add 2 compute
6. Add 1 cinder
7. Add 3 ceph
8. Change disk configuration for both Ceph nodes. Change 'Ceph' volume for vdc
9. Verify networks
10. Deploy the environment
11. Verify networks
12. Run OSTF tests
13. Launch instance in Horizon
14. Connect to VNC console

Compute node has default DROP rule in INPUT iptables chain, and drop connection from vncproxy

# iptables -L INPUT -n -v | grep INPUT
Chain INPUT (policy DROP 32 packets, 2448 bytes)

2015-12-30 14:28:26.445 54384 INFO nova.console.websocketproxy [req-3783a8fb-ed04-4df4-b241-55a1f46c7f62 - - - - -] 3: connecting to: 192.168.0.9:5900
2015-12-30 14:30:33.725 54384 INFO nova.console.websocketproxy [req-3783a8fb-ed04-4df4-b241-55a1f46c7f62 - - - - -] handler exception: [Errno 110] ETIMEDOUT

After add ACCEPT rule for 5900-6100 ports in INPUT chain on compute Horizon connects to VNC successfully

[Dmitry Tyzhnenko (dtyzhnenko)]

It seems to be happened after the merge this review [1]

[1] https://review.openstack.org/#/c/258050

[Maciej Relewicz (rlu)]

should be fixed by https://review.openstack.org/#/c/262255/

[Maciej Relewicz (rlu)]

it's duplicate: https://bugs.launchpad.net/fuel/+bug/1529112

[Artem Panchenko (apanchenko-8)]

@rlu

LP has 'Mark as duplicate' option, let's use it ;)