Comment 3 for bug 834633

I can verify this path fixes the exception while starting an instance.

But - There is another bug preventing the address from being disassociated + released correctly on termination, which in turn leaves the address attached to a non-existent instance.

2011-10-10 15:58:21,785 DEBUG nova.network.manager [5220cafc-9da7-4000-a164-2089b2ec1079 kiall managedit] floating IP deallocation for instance |49| from (pid=1105) deallocate_for_instance /usr/lib/python2.7/dist-packages/nova/network/manager.py:251
2011-10-10 15:58:21,833 ERROR nova.rpc [-] Exception during message handling
(nova.rpc): TRACE: Traceback (most recent call last):
(nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py", line 620, in _process_data
(nova.rpc): TRACE: rval = node_func(context=ctxt, **node_args)
(nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/nova/network/manager.py", line 265, in deallocate_for_instance
(nova.rpc): TRACE: True)
(nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/nova/network/api.py", line 68, in release_floating_ip
(nova.rpc): TRACE: raise exception.ApiError(_('Floating ip is in use. '
(nova.rpc): TRACE: ApiError: Floating ip is in use. Disassociate it before releasing.