novnc fails when amqp_rpc_single_reply_queue=True
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Unassigned | ||
Grizzly |
Fix Released
|
High
|
Nikola Đipanov |
Bug Description
When amqp_rpc_
Reproduce by starting more then one instance, and then get theit vnc consoles with:
$ nova get-vnc-consol $INSTANCE_UUID_1 novnc
$ nova get-vnc-consol $INSTANCE_UUID_2 novnc
And try to connect to those consoles in your browser, to use them, and refresh the page. The page will eventually get stuck on 'Waiting for VNC handshake' and generaly not work properly.
I dug a bit deeper into this and it seems to be realted to a select call in wbesockify.py which does not work properly with eventlet monkey_patched sockets.
The solution is to either not monkey_patch for /cmd/nova-
Confirmed with trunk on 75ead3a2a37efbc
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
assignee: | nobody → Nikola Đipanov (ndipanov) |
milestone: | none → havana-2 |
Changed in nova: | |
importance: | Critical → High |
Changed in nova: | |
milestone: | havana-2 → havana-3 |
Changed in nova: | |
milestone: | havana-3 → havana-2 |
Changed in nova: | |
milestone: | havana-2 → 2013.2 |
Also this fails even worse with Grizzly as there is no monkey patching on nova-novncproxy. see https:/ /review. openstack. org/#/c/ 33319/