yahoo-eng-team team mailing list archive

[Matthew Booth <mbooth@xxxxxxxxxx>]

Public bug reported:

If fixed IP allocation fails, for example because nova's network
interfaces got renamed after a reboot, nova will loop continuously
trying, and failing, to create a new instance. For every attempted spawn
the instance will end up with an additional fixed IP allocated to it.
This is because the code is associating the IP, but not disassociating
it if the function fails.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1328539

Title:
  Fixed IP allocation doesn't clean up properly on failure

Status in OpenStack Compute (Nova):
  New

Bug description:
  If fixed IP allocation fails, for example because nova's network
  interfaces got renamed after a reboot, nova will loop continuously
  trying, and failing, to create a new instance. For every attempted
  spawn the instance will end up with an additional fixed IP allocated
  to it. This is because the code is associating the IP, but not
  disassociating it if the function fails.

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