Can't boot instances in new tenant, fixed ips [closed]

asked 2014-04-22 10:53:29 -0600

serverascode gravatar image

updated 2014-04-22 15:56:14 -0600

Hi All -- I can't create new instances in new tenants. The instance comes up as an error.

I'm running a small OpenStack Essex (yup back on Essex). I added a new tenant, but that new tenant can't create instances, they end up in an ERROR status.

$ nova list
+--------------------------------------+------------+--------+------------+-------------+----------+
| ID                                   | Name       | Status | Task State | Power State | Networks |
+--------------------------------------+------------+--------+------------+-------------+----------+
| e2ebe076-a765-4816-8cd6-0195b8d1ed73 | isttest2-1 | ERROR  | deleting   | NOSTATE     |          |
| 34017d0c-f6e4-4db8-8816-597a1e99ee8e | isttest2-2 | ERROR  | deleting   | NOSTATE     |          |
| a7231b73-b9f9-4a79-8338-3687e4133633 | isttest2-5 | ERROR  | deleting   | NOSTATE     |          |
+--------------------------------------+------------+--------+------------+-------------+----------+

This is a traceback I get on the compute nodes.

    2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4] Traceback (most recent call last):
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 617, in _spawn
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]     self._legacy_nw_info(network_info), block_device_info)
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]   File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 114, in wrapped
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]     return f(*args, **kw)
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line 946, in spawn
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]     block_device_info=block_device_info)
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line 1568, in to_xml
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]     rescue, block_device_info)
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line 1451, in _prepare_xml_info
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]     nics.append(self.vif_driver.plug(instance, network, mapping))
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 99, in plug
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]     return self._get_configurations(network, mapping)
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 69, in _get_configurations
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]     'ip_address': mapping['ips'][0]['ip'],
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4] IndexError: list index out of range
2014-04-21 17:35:05 TRACE nova.compute.manager [instance: e1f0d1ef-ede5-4c6e-b47b-9454aacbecb4]

I believe it is similar to this bug: https://bugs.launchpad.net/nova/+bug/...

NOTE: When I first created the OpenStack cluster, I created 100 networks, some of which I deleted, and then later on, after adding new tenants, created new networks. But the new tenant is not able to use the new network.

I think I need to perhaps clean up the fixed_ips table in nova? If so I'm not exactly sure what to do. Can I just delete the entries in fixed_ips and then will nova-network recreate them?

Thanks for any help.

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by rbowen
close date 2016-12-07 15:50:27.866752

Comments

This question is about a version of OpenStack long since EOL'ed. Closing.

rbowen gravatar imagerbowen ( 2016-12-07 15:50:23 -0600 )edit