yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #86938
[Bug 1933502] Re: L3 DB FloatingIP callbacks improvements
Reviewed: https://review.opendev.org/c/openstack/neutron/+/801453
Committed: https://opendev.org/openstack/neutron/commit/b488fb8e223498703eed158e741c72d7ce03fe16
Submitter: "Zuul (22348)"
Branch: master
commit b488fb8e223498703eed158e741c72d7ce03fe16
Author: Szymon Wroblewski <szymon.wroblewski@xxxxxxxxxxxx>
Date: Mon Jul 19 12:25:32 2021 +0200
Use payloads for FloatingIP AFTER callbacks
Change FloatingIP AFTER_ notifications in l3_db to use publish calls.
Move association_event field into Payload metadata.
Closes-Bug: #1933502
Change-Id: Ie4c0f4a63a87c32026c49b03068e5f461deb38b6
** 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/1933502
Title:
L3 DB FloatingIP callbacks improvements
Status in neutron:
Fix Released
Bug description:
FloatingIP change notifications in l3_db use obsolete notify calls
(instead of publish) and form that isn't compatible with
OVOServerRpcInterface, which makes usage of RemoteResourceCache for
FloatingIP by agents quite difficult.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1933502/+subscriptions
References