auto_assign_floating_ip fails with raceback in nova-network.log

Bug #941216 reported by Adam Gandelman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
New
Undecided
Unassigned

Bug Description

When auto_assign_floating_ip flag is specified, the corresponding function fails on instance spawn. It seems the allocate_for_instance() method is expecting an outdated data structure to be returned as nw_info:

2012-02-26 01:53:24 DEBUG nova.network.manager [-] QUOTA: 1 from (pid=1555) allocate_floating_ip /opt/stack/nova/nova/network/manager.py:375
2012-02-26 01:53:24 ERROR nova.rpc.common [-] Exception during message handling
(nova.rpc.common): TRACE: Traceback (most recent call last):
(nova.rpc.common): TRACE: File "/opt/stack/nova/nova/rpc/amqp.py", line 250, in _process_data
(nova.rpc.common): TRACE: rval = node_func(context=ctxt, **node_args)
(nova.rpc.common): TRACE: File "/opt/stack/nova/nova/network/manager.py", line 239, in wrapped
(nova.rpc.common): TRACE: return func(self, context, *args, **kwargs)
(nova.rpc.common): TRACE: File "/opt/stack/nova/nova/network/manager.py", line 302, in allocate_for_instance
(nova.rpc.common): TRACE: for nw, info in nw_info:
(nova.rpc.common): TRACE: ValueError: too many values to unpack
(nova.rpc.common): TRACE:
2012-02-26 01:53:24 ERROR nova.rpc.common [-] Returning exception too many values to unpack to caller

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.