yahoo-eng-team team mailing list archive

[Rossella Sblendido <rsblendido@xxxxxxxx>]

This is the expected behavior. This change https://review.openstack.org/58017 modified the way IP are recycled.
Instead of being recycled immediately after the release of a port, the complex operation of rebuilding the availability table is performed  when the table is exhausted

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1332481

Title:
  Creating and deleting the vm port multiple times the allocated ips are
  not used automatically

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  DESCRIPTION: Creating and deleting the vm port multiple times the
  allocated ips are not reused while spawning the new vm port

  Steps to Reproduce: 
  1. Create a network. 
  2. Create a subnet 10.10.1.0/24
  3. Spawned a vm make sure vm got the ip.  (say 10.10.1.2)
  4. Delete the vm 
  5. Spawned another vm make sure its gets the ip .
  6. Make sure in the port list the previous allocated ip is not listed.

  Actual Results: VM get the next  ip (10.10.1.3 ) not the ip that got
  released.

  Expected Results: VM should get the relased ips.

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