Hi, can you try with the flag: force_dhcp_release=false But first you need to: > Manually set instance_id=NULL in the fixed_ips table allows things to > work again.
Belmiro CERN On Jun 23, 2012, at 5:11 AM, Lars Kellogg-Stedman wrote: > When an instance terminates, the "allocated" field in the fixed_ips is > set to "0", but the "instance_id" field remains set. Once all the > addresses are in this state, new instances fail to start, and the > following error is logged by nova-network: > > 2012-06-22 23:09:34 ERROR nova.rpc.amqp > [req-1fea207d-cd65-4375-9a04-17ba1ab92e3e > 22bb8e502d3944ad953e72fc77879c2f 76e2726cacca4be0bde6d8840f88c136] > Returning exception Zero fixed ips available. to caller > > Which shows up in compute.log as: > > 2012-06-22 23:08:35 TRACE nova.rpc.amqp RemoteError: Remote error: > NoMoreFixedIps Zero fixed ips available. > > Manually set instance_id=NULL in the fixed_ips table allows things to > work again. > > We're running the 2012.1.1 release and we're using the FlatDHCP model. > Is this a known bug? > > Thanks, > > -- > Lars Kellogg-Stedman <l...@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@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
