yahoo-eng-team team mailing list archive

[Alan Pevec <1193031@xxxxxxxxxxxxxxxxxx>]

** Changed in: nova/grizzly
       Status: Fix Committed => Fix Released

-- 
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/1193031

Title:
  novnc fails when amqp_rpc_single_reply_queue=True

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) grizzly series:
  Fix Released

Bug description:
  When amqp_rpc_single_reply_queue=True is set, using qpid on Fedora 17
  novn service will fail to work reliably.

  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-novncproxy
  and do the rpc call that validates the token with the consolauth
  service in a separate process that is monkey_patched (the rpc won't
  work without it), or to make openstack/common/rpc/amqp/multicall not
  use green-threads for this particular call (ie. block the caller).

  Confirmed with trunk on 75ead3a2a37efbc6a4fdea7e492ca41cdd559a8c
  (20-6-2013)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1193031/+subscriptions