yahoo-eng-team team mailing list archive

[Sridhar Venkat <svenkat@xxxxxxxxxx>]

Public bug reported:

When a new VM is spawned with no ip address in network request, neutron
allocates a new ip address from corresponding subnet pool. And it does
not pick next available ip. Instead of PreferNextAddressRequest,
AnyAddressRequest is set for ip_request.

This is due to neutron/ipam/request.py
AddressRequestFactory.get_request() returns AnyAddressRequest under
final else clause. It is preferred that it returns
PreferNextAddressRequest so that IP addresses are allocated in a
sequential pattern.

** Affects: neutron
     Importance: Undecided
     Assignee: Sridhar Venkat (svenkat)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Sridhar Venkat (svenkat)

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

Title:
  IPAM returns random ip address instead of next IP from subnet pool

Status in neutron:
  New

Bug description:
  When a new VM is spawned with no ip address in network request,
  neutron allocates a new ip address from corresponding subnet pool. And
  it does not pick next available ip. Instead of
  PreferNextAddressRequest, AnyAddressRequest is set for ip_request.

  This is due to neutron/ipam/request.py
  AddressRequestFactory.get_request() returns AnyAddressRequest under
  final else clause. It is preferred that it returns
  PreferNextAddressRequest so that IP addresses are allocated in a
  sequential pattern.

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