summaryrefslogtreecommitdiffstats
path: root/nova/notifications.py
diff options
context:
space:
mode:
authorPhil Day <philip.day@hp.com>2012-07-11 09:26:11 +0100
committerPhil Day <philip.day@hp.com>2012-07-12 16:15:39 +0100
commit34f9d7e974d0e09c723e0a04ed6eecd1b482e77d (patch)
tree23e1f85bbae6993342c49af44294c6137ca531fe /nova/notifications.py
parent74a7294cf68ad64367620caac52c7670d6d379ca (diff)
downloadnova-34f9d7e974d0e09c723e0a04ed6eecd1b482e77d.tar.gz
nova-34f9d7e974d0e09c723e0a04ed6eecd1b482e77d.tar.xz
nova-34f9d7e974d0e09c723e0a04ed6eecd1b482e77d.zip
Convert remaining network API casts to calls
Fix for Bug 1021340 During compute/terminate_instance networking is de-allocated by a call to network/api/deallocate_for_instance(), which is implemented as an rpc.cast to the network manager. This in turn will eventually call network/manager/deallocate_fixed_ip(), which in turn call the compute API to trigger a security group refresh, which will get the instance from the database However because original call to the network manager is a cast there is a chance that the compute manager will delete the instance record in the DB before the compute API (in the network manager) tries to retrieve the instance. At this point the security group refresh fails (leaving rules in place which are a security risk when the IP is reused), and potentially stopping otheraspects of the network deallocation from completing. Changing this from rpc.call to rpc.cast will fix this issue. Aside from this specific use of a cast there are 4 other casts in the network API: add_fixed_ip_to_instance remove_fixed_ip_from_instance add_network_to_project release_floating_ip and to avoid other timing issues these will also be converted to calls. Change-Id: I5cdcc628293d3e7cf165c5ffe4883f138783f73f
Diffstat (limited to 'nova/notifications.py')
0 files changed, 0 insertions, 0 deletions