yahoo-eng-team team mailing list archive

[OpenStack Infra <1627628@xxxxxxxxxxxxxxxxxx>]

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

commit cd7d63bde92e47a4b7bd4212b2e6c45f08c03143
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Sat Sep 24 23:07:45 2016 -0700

    Refetch subnet/network from DB in ML2 update ops
    
    This ensures that any extensions run in the ML2 extension framework
    that bump the revision number of the subnet or network result in the
    altered revision number being returned to the API caller and passed
    into the ML2 mech drivers and callback handlers.
    
    Closes-Bug: #1627628
    Change-Id: Ieb37a3833ee52c671419c6dc981cf91c2366ae94


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

Title:
  ml2 update_network/subnet returning stale info

Status in neutron:
  Fix Released

Bug description:
  update_network and update_subnet need similar fixes as the one for bug
  1625981. if an extension makes a change, the revision number bump is
  not reflected in the update result

  This can be seen by updating the dns_domain on a network with the dns
  extension. The update result will not have a bumped revision number
  even though the revision number was incremented.

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