[OPNFLWPLUG-540] Openflow clustering: Possibility to miss the event during switchover Created: 26/Aug/15  Updated: 27/Sep/21  Resolved: 23/Aug/16

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

Type: Bug
Reporter: Hariharan Sethuraman Assignee: Unassigned
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: 4190

 Description   

Having ongoing openflow clustering design, the event can be missed in the following scenario.

1) Lets say we have 3 controllers connected to a switch (presume handshake happens from 3 controllers). And lets say controller 1 is the master.
2) A port down event sent from switch to controller 1 and controller 1 crashed without handling it.
3) Switchover happens from controller 1 to controller 2
4) When controller 2 takes up the leadership, it wont query for port status and start handling subsequent events. The port down event is missed!
5) UI will show port up while the port is down in network



 Comments   
Comment by Jozef Bacigal [ 23/Aug/16 ]

This is old bug and it has been a much changed since then. Now if mastership is changed controller always make an initial commit where is also PORT STATUS check.

This problem should not be a problem anymore.

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