231010bdf2
Currently treat_devices_added_or_updated in the OVS agent skips
processing devices which disappeared from the integration bridge
during the agent loop.
This is fine, however the agent should not mark these devices as
processed. Otherwise they won't be processed, should they appear
again on the bridge.
This patch ensures these devices are not added to the current
device set.
The patch also changes treat_devices_added_or_updated. The
function now will return the list of skipped devices and not
anymore a flag signalling whether a resync is required.
With the current logic a resync would be required if retrieval
of device details fails. With this change, the function
treat_devices_added_or_updated will raise in this case and the
exception will be handled in process_network_ports.
For the sake of consistency, this patch also updates the
similar function treat_ancillary_devices_added in order to
use the same logic.
Finally, this patch amends an innaccurate related comment.
Closes-Bug: #1329546
Conflicts:
neutron/plugins/openvswitch/agent/ovs_neutron_agent.py
Required changes:
- fetch all device details first before proceeding with handling ports
to reflect Juno behaviour.
- unit test was modified to run with get_device_details since
get_devices_details_list is not available in Icehouse.
- fixed E128 violation in the backported code.
Change-Id: Icc744f32494c7a76004ff161536316924594fbdb
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_agent_scheduler.py | ||
| test_openvswitch_plugin.py | ||
| test_ovs_db.py | ||
| test_ovs_defaults.py | ||
| test_ovs_lib.py | ||
| test_ovs_neutron_agent.py | ||
| test_ovs_rpcapi.py | ||
| test_ovs_security_group.py | ||
| test_ovs_tunnel.py | ||