[OPNFLWPLUG-912] Regression on multiple connection handling (split connection) Created: 20/Jun/17  Updated: 27/Sep/21  Resolved: 23/Aug/17

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

Type: Bug
Reporter: Len Assignee: Jozef Bacigal
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: 8723

 Description   

Establish two connections to the controller from the same switch, The controller should accept both connections.
Code has been pushed into stable carbon to support this. this works in Carbon release but not with latest Carbon code.

This can be reproduced by:

  • Start a single node carbon based controller with an OVS switch using mininet
  • Establish two conections to the same controller using ovs-vsctl set-controller <bridge> tcp: <controller-IP-Address> : <port> tcp: <controller-IP-Address> : <port>
  • sudo ovs-vsctl set-controller s1 tcp:<controller-IP-Address>:6633 tcp:<controller-IP-Address>:6653
  • This will succeed on Carbon release but fail on Carbon latest code

 Comments   
Comment by Jozef Bacigal [ 29/Jun/17 ]

Can you please try with this patch ?

https://git.opendaylight.org/gerrit/#/c/59557/

Comment by Luis Gomez [ 25/Jul/17 ]

This is what I see with current implementations (both are failing the test:

Boron:

  • 2 connections same DP id: connections bounces, none gets master.
  • Back to 1 connection: original conection is rejected because controller does not respond switch echo message.

Carbon:

  • 2 connection: new connection becomes master and original connection becomes slave.
  • Back to 1 connection: original connection is always slave.
Generated at Wed Feb 07 20:33:42 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.