Reviewed: https://review.openstack.org/386848 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7fdb98cf174ead0ba75d3fad13c89d5c55e40ff2 Submitter: Jenkins Branch: master
commit 7fdb98cf174ead0ba75d3fad13c89d5c55e40ff2 Author: Brandon Logan <[email protected]> Date: Fri Oct 14 18:19:54 2016 -0500 Pecan: rework notifier hook for registry callbacks [1] and [2] were added to use the registry callback notifier for dhcp and nova notifications for the legacy wsgi layer. This adds the same functionality to the pecan wsgi layer. It just so happens to clean the code up nicely and also fixes a bug that was introduced by [3] that caused an ever increasing number of subscriptions to the registry callback notifier. [1] I7440becb6d30af7159ecaeba09d7a28eceb71bea [2] I1d7d4b80ee77deefce18df22f76cab81750c0397 [3] I607635601caff0322fd0c80c9023f5c4f663ca25 Change-Id: I0a8b64e7742283a9d6c6b42ebc27887836df69ec Closes-Bug: #1633296 ** 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/1633296 Title: Pecan tempest API test jobs timeout Status in neutron: Fix Released Bug description: Looks like its because of a ton of dhcp notifications being sent out. The problem being that pecan tries to grab the plugins dhcp notifier, but fails, so it instantiates its own. This happens for every request, and when the dhcp notifier is instantiated it subscribes to notifications. This means, with pecan instantiating a new dhcp notifier for every request, the subscriptions keep growing and growing. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1633296/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
