yahoo-eng-team team mailing list archive

[Angus Lees <1362416@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

midonet "delete_dhcp" function doesn't check subnet length when
searching for the DHCP entries to delete.  This means it can delete the
wrong subnet entry if two are nested (ie: have the same prefix, but
different lengths).

Disclaimer: I don't have midonet equipment and don't know if it is even
capable of supporting nested DHCP subnets - I just found this while
wondering why 'net_len' variable was unused.

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  midonet: Deletes incorrect nested DHCP subnet

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  midonet "delete_dhcp" function doesn't check subnet length when
  searching for the DHCP entries to delete.  This means it can delete
  the wrong subnet entry if two are nested (ie: have the same prefix,
  but different lengths).

  Disclaimer: I don't have midonet equipment and don't know if it is
  even capable of supporting nested DHCP subnets - I just found this
  while wondering why 'net_len' variable was unused.

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