← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1536998] Re: DHCP Port update notification not sent when an IPv6 auto_address subnet is created on an existing IPv4 network.

 

Reviewed:  https://review.openstack.org/271223
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=488ef69cfd30af73c340ddd9b32ad554579e8a6d
Submitter: Jenkins
Branch:    master

commit 488ef69cfd30af73c340ddd9b32ad554579e8a6d
Author: sridhargaddam <sgaddam@xxxxxxxxxx>
Date:   Fri Jan 22 10:18:30 2016 +0000

    Trigger dhcp port_update for new auto_address subnets
    
    When an ipv6 auto_address subnet is added to an existing network with IPv4
    subnet, the dhcp port in the network is simply updated with an IPv6 address.
    However, neutron does not send any port_update notification for the dhcp
    port. This causes inconsistencies (while configuring anti-spoofing rules)
    for external controllers (like OpenDaylight) as the dhcp port info
    in controller does not match with the dhcp port info in Neutron db.
    This patch addressess this issue by having the plugin send a port_update
    call when the dhcp port is updated with IPv6 auto address.
    
    Closes-Bug: #1536998
    Change-Id: I08d257d6d66f95c609a4429e45fde026b42f3fa1


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  DHCP Port update notification not sent when an IPv6 auto_address
  subnet is created on an existing IPv4 network.

Status in neutron:
  Fix Released

Bug description:
  When an ipv6 auto_address subnet is added to an existing network with IPv4
  subnet, the dhcp port in the network is simply updated with an IPv6 address.
  However, neutron does not send any port_update notification for the dhcp
  port. This causes inconsistencies (while configuring anti-spoofing rules)
  for external controllers (like OpenDaylight) as the dhcp port info
  in controller does not match with the dhcp port info in Neutron db.

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


References