Open Stack

I found new RPMs, generated just yesterday (May 22). I upgraded using them and 
the problem persists.

The packages were:

openstack-quantum-2013.1.1-3.el6.noarch                           82 k
openstack-quantum-linuxbridge-2013.1.1-3.el6.noarch              147 k
python-quantum-2013.1.1-3.el6.noarch                             2.7 M

It is reporting slightly differently. This is from linuxbridge.log:


ERROR [quantum.openstack.common.rpc.amqp] Exception during message handling
Traceback (most recent call last):
   File 
"/usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/amqp.py", line 
430, in _process_data
     rval = self.proxy.dispatch(ctxt, version, method, **args)
   File "/usr/lib/python2.6/site-packages/quantum/common/rpc.py", line 43, in 
dispatch
     quantum_ctxt, version, method, **kwargs)
   File 
"/usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/dispatcher.py", 
line 133, in dispatch
     return getattr(proxyobj, method)(ctxt, **kwargs)
   File "/usr/lib/python2.6/site-packages/quantum/db/agents_db.py", line 173, 
in report_state
     plugin.create_or_update_agent(context, agent_state)
   File "/usr/lib/python2.6/site-packages/quantum/db/agents_db.py", line 145, 
in create_or_update_agent
     context, agent['agent_type'], agent['host'])
   File "/usr/lib/python2.6/site-packages/quantum/db/agents_db.py", line 121, 
in _get_agent_by_type_and_host
     Agent.host == host).one()
TypeError: <lambda>() takes exactly 2 arguments (3 given)


The configured RPC backend is quantum.openstack.common.rpc.impl_kombu, which I 
believe is the default.

The rabbitmq-server is from package rabbitmq-server-2.6.1-1.el6.noarch.

Are there any configuration settings I should check?

On 05/22/2013 06:42 PM, gong yong sheng wrote:
> It seems there is a gap between these two packages, can u upgrade the openstack
> quantum to latest git repo?
> On 05/23/2013 08:08 AM, Craig E. Ward wrote:
>> I'm configuring a single-node installation of the Grizzly release and I am
>> having some strange issues with the Quantum agents.
>>
>> The install using quantum-linuxbridge-agent, quantum-l3-agent, and
>> quantum-dhcp-agent. Each on is logging the error:
>>
>>    Failed reporting state!
>>
>> The end of the stack trace indicates that the number arguments to some call
>> was incorrect.
>>
>> dhcp-agent:        TypeError: <lambda>() takes exactly 2 arguments (3 given)
>> l3_agent:          TypeError: <lambda>() takes exactly 2 arguments (3 given)
>> linuxbridge-agent: TypeError: <lambda>() takes exactly 2 arguments (3 given)
>>
>> The services are connecting to the RabbitMQ server. Does this indicate a
>> mismatch in some driver that sites between the agents and the RabbitMQ server?
>>
>> Has anyone else seen this type of error before?
>>
>> The packages I'm using are openstack-quantum-2013.1-3.el6.noarch and
>> openstack-quantum-linuxbridge-2013.1-3.el6.noarch.
>>
>> Any suggestions will be appreciated.
>>
>> Thanks,
>>
>> Craig
>>

-- 
Craig E. Ward
USC Information Sciences Institute
310-448-8271
cward at ISI.EDU