Deleted fixed network causes vm failure

Bug #1086464 reported by JB
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Won't Fix
Medium
Raildo Mascena de Sousa Filho

Bug Description

Using Essex 2012.1.3

1) Created fixed ip network 192.168.7.0/24
This created an entry in both fixed_ips and networks.

2) deleted using nova-manage network delete 192.168.7.0/27

3) again created the same network

4) When I launch a VM, I am seeing "Network 1 not found " error.
In the database, nova->networks table, there is no network entry with id =1 and all the entries in fixed_ips for network id=1 are set to deleted="t".

I had to manually delete network and all the entries in fixed_ips in the database. After that I had to recreate the network. Then, it worked.

Revision history for this message
JB (jaybeltur) wrote :
Download full text (5.3 KiB)

Though deleting the fixed network, sets the deleted flag in fixed_ips table to 't', lauching of VM fails because mapping cache does not get cleared. Launching throws this error.
2012-12-04 15:24:58 ERROR nova.compute.manager [req-77dd564a-3a5a-4c5c-8c33-5d5a8feb57ee 7e47b69879624465a81e1adad43dbcd2 ccb0ab914f6e49f2923632ce3b810447] [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] Instance failed to spawn
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] Traceback (most recent call last):
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 617, in _spawn
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] self._legacy_nw_info(network_info), block_device_info)
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 114, in wrapped
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] return f(*args, **kw)
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line 918, in spawn
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] block_device_info=block_device_info)
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line 1527, in to_xml
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] rescue, block_device_info)
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line 1410, in _prepare_xml_info
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] nics.append(self.vif_driver.plug(instance, network, mapping))
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 100, in plug
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] return self._get_configurations(network, mapping)
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 70, in _get_configurations
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] 'ip_address': mapping['ips'][0]['ip'],
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50] IndexError: list index out of range
2012-12-04 15:24:58 TRACE nova.compute.manager [instance: 4a1efa1f-c526-4d25-841c-e4d893379b50]
2012-12-04 15:24:58 ERROR nova.utils [req-77dd564a-3a5a-4c5c-8c33-5d5a8feb57ee 7e47b69879624465a81e1adad43dbcd2 ccb0a...

Read more...

Michael Still (mikal)
Changed in nova:
status: New → Triaged
importance: Undecided → Medium
Changed in nova:
assignee: nobody → Raildo Mascena de Sousa Filho (raildo)
Revision history for this message
Raildo Mascena de Sousa Filho (raildo) wrote :

I'm trying to simulate the bug and I create a network using nova-manage, deleted and created again. when i going to launch a VM, it worked fine.

The proper way is using the new-manage to create a network or should be done differently? If yes, how else should I do to simulate this error?

Revision history for this message
Raildo Mascena de Sousa Filho (raildo) wrote :

I tried to simulate this bug and I'm fail,but this bug occurred in an older version (Essex 2012.1.3). At this time, the packages Nova and Neutron were together, today they are separated. I think that after such separation, the error no longer occurs, and this bug should be finalized. One would look better and make sure that it can close this bug?

Revision history for this message
Joe Gordon (jogo) wrote :

Essex is not supported anymore.

Changed in nova:
status: Triaged → Won't Fix
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.