Launching instance fails in Precise A2 - network/manager.py too many values to unpack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
John Griffith |
Bug Description
I've an out-of-the-box install of Precise A2 which is failing to spin up instances with the following messages in nova-compute.log and nova-network.log
Details replicated here: http://
And relevant paste here http://
Overview:
Single host, Precise A2
eth0 10.10.0.0/16
eth1 172.15.0.0/16
VLAN network, tied to eth0, gives vlan4025.
created networks with the following
1. created relevant user, roles and tenants in keystone, etc.
2. uploaded image to glance
3. created appropriate default security group settings
4. launched instance
5. err spewed
012-02-08 11:02:04,345 DEBUG nova.utils [-] Got semaphore "get_dhcp" for method "_get_dhcp_ip"... from (pid=3270) inner /usr/lib/
2012-02-08 11:02:04,436 DEBUG nova.network.
2012-02-08 11:02:04,521 ERROR nova.rpc [-] Exception during message handling
(nova.rpc): TRACE: Traceback (most recent call last):
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: rval = node_func(
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: return func(self, context, *args, **kwargs)
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: for nw, info in nw_info:
(nova.rpc): TRACE: ValueError: too many values to unpack
(nova.rpc): TRACE:
2012-02-08 11:02:04,522 ERROR nova.rpc [-] Returning exception too many values to unpack to caller
2012-02-08 11:02:04,522 ERROR nova.rpc [-] ['Traceback (most recent call last):\n', ' File "/usr/lib/
Changed in nova: | |
importance: | Undecided → High |
milestone: | none → essex-4 |
Changed in nova: | |
milestone: | essex-4 → essex-rc1 |
Changed in nova: | |
assignee: | nobody → John Griffith (john-griffith) |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
On looking at nova-manage floating-list now it shows my attempts, but equally it seems to at least attempt to go some way to allocate the public floating ip:
root@openstack1:~# nova-manage floating list 4915-4321- 8b1a-cec8cde3bc e8 None None] backend <module 'nova.db. sqlalchemy. api' from '/usr/lib/ python2. 7/dist- packages/ nova/db/ sqlalchemy/ api.pyc' > from (pid=14755) __get_backend /usr/lib/ python2. 7/dist- packages/ nova/utils. py:588 7883ad0d142c860 3c 172.15.1.1 None nova eth1 7883ad0d142c860 3c 172.15.1.2 None nova eth1 7883ad0d142c860 3c 172.15.1.3 None nova eth1 7883ad0d142c860 3c 172.15.1.4 None nova eth1 7883ad0d142c860 3c 172.15.1.5 None nova eth1
2012-02-08 13:16:55,769 DEBUG nova.utils [req-07ce2122-
15a82b3d665d4fd
15a82b3d665d4fd
15a82b3d665d4fd
15a82b3d665d4fd
15a82b3d665d4fd
None 172.15.1.6 None nova eth1
None 172.15.1.7 None nova eth1
None 172.15.1.8 None nova eth1
None 172.15.1.9 None nova eth1
None 172.15.1.10 None nova eth1
None 172.15.1.11 None nova eth1
None 172.15.1.12 None nova eth1