[NETVIRT-518] SubnetRoute re-election must happen when the anchor switch for subnetRoute remains disconnected Created: 08/Mar/17  Updated: 03/Apr/17  Resolved: 03/Apr/17

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Boron
Fix Version/s: None

Type: Bug
Reporter: Vivekanandan Narasimhan Assignee: Vivekanandan Narasimhan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 7931

 Description   

SubnetRoute re-election must happen when the anchor switch for subnetRoute remains disconnected.

More summarily:
Subnet Route reelection algorithm is triggered today only when
the anchor ports on the subnet go to DOWN state (or) if such
anchor ports on the subnet are being removed.

However, there are situations where a switch hosting the anchor
port can be disconnected on the openflow control-path and can
continue to remain so indefinitely.

Under such circumstance, new non-neutron IPs become undiscoverable
as the switch hosting the anchor port cannot punt discoverable IP
packets to the controller.

So this fix attempts to always trigger reelection of nodes for
subnetRoute hosting as soon as the current anchor node(or switch)
is detected to be disconnected from the controller.



 Comments   
Comment by Vivekanandan Narasimhan [ 08/Mar/17 ]

The fix is here: https://git.opendaylight.org/gerrit/#/c/52989/

Generated at Wed Feb 07 20:21:46 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.