ml2: too many port_update notifications sent because of port binding
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Salvatore Orlando |
Bug Description
process_
However, its current implementation: https:/
Return True, hence triggering a notification in many cases.
The code has a check for returning false when the host is not set and the vif is already bound: https:/
However, this is perhaps not triggered in many cases.
As an example, in this job: http://
Of 538 update_port calls to the plugin, process_
It is therefore worth ensuring no notification is sent if the host doesn't change (the other binding parameters should not change on update and even if they can they should not trigger a notification) in 72 cases out of 82 cases where the flag was false before invoking process_
Looking at the logs - the port should not have been notified because of bindings in any case.
Changed in neutron: | |
milestone: | icehouse-1 → icehouse-2 |
Changed in neutron: | |
status: | New → In Progress |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | icehouse-2 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/58860
Review: https:/