Astara

astara router driver causes config reload for every .end event.

Bug #1556294 reported by Mark McClain
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Astara
Fix Released
Medium
Mark McClain
Astara mitaka-rc1

Bug Description

The router driver currently triggers an config reload for ".end" even the ones that do not impact the router. Digging through the source, this handling has been present for a some time and was likely not noticed when Neutron managed less entities than it does today.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to astara (master)

Fix proposed to branch: master
Review: https://review.openstack.org/291929

Changed in astara:
status: New → In Progress
Adam Gandelman (gandelman-a)
Changed in astara:
milestone: none → mitaka-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to astara (master)

Reviewed: https://review.openstack.org/291929
Committed: https://git.openstack.org/cgit/openstack/astara/commit/?id=d55ffba18086623815acabc26ea2865c48a7ec4d
Submitter: Jenkins
Branch: master

commit d55ffba18086623815acabc26ea2865c48a7ec4d
Author: Mark McClain <email address hidden>
Date: Fri Mar 11 17:12:35 2016 -0500

    Properly limit router driver event processing

    This change limits the number of update events generated for a router by
    removing the catch-all conditional that previously applied. In
    addition, floatingip events were added as intersting events for a
    router.

    Change-Id: I67c3082d8b9f3ad3e47d65f6c13ef05c06d4d6d1
    Closes-Bug:1556294

Changed in astara:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.