yahoo-eng-team team mailing list archive

[Mark McClain <1200132@xxxxxxxxxxxxxxxxxx>]

Closing this bug and will consider adding support as part of the IPAM
refactoring.

** Changed in: neutron
   Importance: Undecided => Wishlist

** Changed in: neutron
       Status: New => Won't Fix

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

Title:
  Port update allows fixed_ip to be updated outside of ip allocation
  range

Status in OpenStack Neutron (virtual network service):
  Won't Fix

Bug description:
  DHCP pool (allocation pool) is defined 192.168.1.10-192.168.1.50,
  subnet is 192.168.1.0/24, but I can update the port fixed_ip to
  192.168.1.100.

  _test_fixed_ips_for_port() function that gets called as part of the
  update process only checks if IP is vaild on Subnet, not if it is
  within the allocation pool.

  delete_port() will check to see if it is within the allocation pool
  and not delete it if it isn't. I thought it would be easy enough to
  add QuantumDbPluginV2._check_ip_in_allocation_pool() to
  _test_fixed_ips_for_port() which solves the issue, but it looks like
  adding a port to a router calls the update_port to see the IP.

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