yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1246623] Re: metadata server running on mod_wsgi blocks on rpc.call to nova-conductor

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: "Davanum Srinivas \(DIMS\)" <davanum@xxxxxxxxx>
Date: Mon, 23 Mar 2015 11:00:57 -0000
Reply-to: Bug 1246623 <1246623@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova
       Status: Confirmed => Won't Fix

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

Title:
  metadata server running on mod_wsgi blocks on rpc.call to nova-
  conductor

Status in OpenStack Compute (Nova):
  Won't Fix
Status in The Oslo library incubator:
  Won't Fix

Bug description:
  Hi there.

  We are running all the nova apis (osapi, ec2, metadata) under mod_wsgi
  on Apache. With the Havana upgrade, the metadata server (that started
  using nova-conductor) stopped working (it works perfectly outside
  apache though). After further debugging, I've found that it is
  blocking in the get from the dataqueue of the RPC client:
  https://github.com/openstack/nova/blob/stable/havana/nova/openstack/common/rpc/amqp.py#L526

  A workaround was a call to eventlet.monkey_patch() in our WSGI script.
  Shouldn't we call the monkey patch on the amqp.py module directly?

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