Details
-
Bug
-
Status: Resolved
-
Resolution: Done
-
None
-
None
-
None
-
None
-
Operating System: Linux
Platform: All
-
6710
Description
In Carbon, sometimes, when switch is disconnected and reconnected with very small delay between these actions, it's role is incorrectly set (should be MASTER, but is SLAVE).
Reproduction steps (from Luis from bug https://bugs.opendaylight.org/show_bug.cgi?id=6672):
1) start mininet 1 switch (s1) pointing to any of the cluster instances (e.g. 10.13.11.207)
2) Run the following script in the mininet system to bounce connection quickly:
#!/bin/bash
sudo ovs-vsctl del-controller s1
sleep 0.2
sudo ovs-vsctl set-controller s1 "tcp:192.168.0.101"
In local cluster test, I did step 2 twice. First time, role MASTER was successfully set, but second time, role was SLAVE, what is incorrect.
I attached logs from my local testing from node 10.13.11.207.
Attachments
Issue Links
- blocks
-
BGPCEP-540 ClusterSingletonService/EOS race condition
- Resolved
-
OPNFLWPLUG-616 Longevity test rarely goes beyond 6 hours
- Resolved
-
OPNFLWPLUG-759 l2switch addresss tracker does not behave normally when mininet is disconnected and connected with no time in-between
- Resolved
-
OPNFLWPLUG-767 Switch connection bounce generates wrong entity owner in cluster env
- Resolved