yahoo-eng-team team mailing list archive

[Michael Still <mikal@xxxxxxxxxxx>]

** Changed in: nova
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1017013

Title:
  Nova does not release ips when an instance terminates

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  After an instance terminates, the corresponding entry in the fixed_ips
  table has allocated=1 but instance_id still set to the id of the
  terminated instance.  Once all the available addresses are in this
  state, starting new instances fails with the following error in
  network.log:

    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.

  There were suggestions on the mailing list to try setting
  force_dhcp_release to false, but this appears to be the default and
  setting it explicitly did not correct this behavior.

  I am running the 2012.1.1 release on CentOS 6.2 using a FlatDHCP
  model.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1017013/+subscriptions