force_dhcp_release=true should cause the ip to be released immediately, assuming the relevant optional binary from dnsmasq is installed (it is in the package dnsmasq-utils in ubuntu). If it is set to false then the ips should be reclaimed after a set timeout period (ten minutes by default) via a periodic task in the network worker. If they are not being reclaimed properly then there is definitely a bug somewhere, although I have not seen this happening recently myself. On Jun 23, 2012 6:14 PM, "Lars Kellogg-Stedman" <lars at seas.harvard.edu> wrote: > > can you try with the flag: > > force_dhcp_release=false > > It turns out I already had force_dhcp_release set to False. > > I've opened https://bugs.launchpad.net/nova/+bug/1017013 on this > issue. > > -- > Lars Kellogg-Stedman <lars at seas.harvard.edu> | > Senior Technologist | > http://ac.seas.harvard.edu/ > Academic Computing | > http://code.seas.harvard.edu/ > Harvard School of Engineering and Applied Sciences | > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120624/7576c58f/attachment.html>