yahoo-eng-team team mailing list archive

[OpenStack Infra <1714655@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/500269
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8f3c27cd853d9e4d029939cbd8b371bf880c2cae
Submitter: Jenkins
Branch:    master

commit 8f3c27cd853d9e4d029939cbd8b371bf880c2cae
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Sat Sep 2 02:58:48 2017 -0700

    DHCP provisioning block only on port addr update
    
    Don't add a DHCP provisioning block during port updates
    unless the IP address or MAC address has changed. There is
    no point in waiting on the DHCP agent after a port update
    unless the addresses have changed. We already wait on the
    DHCP agent after the port has been initially created so
    we will be guaranteed that a reservation exists for the
    correct MAC/IP in the DHCP agent.
    
    Closes-Bug: #1714655
    Change-Id: Idef5994e274ea99260367edb8331fd10b98a1432


** 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/1714655

Title:
  Optimization in DHCP notifier introduced a race condition

Status in neutron:
  Fix Released

Bug description:
  Change I948132924ec5021a9db78cf17efbba96b2500e8e introduced a race
  condition where a neutron port can be updated without altering any
  fields visible in the dict other than the revision number (e.g.
  binding levels). The port update itself unconditionally places the
  provisioning block so a port can get blocked waiting for the DHCP
  agent when the DHCP agent hasn't been notified.

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