-
Bug
-
Resolution: Won't Do
-
Medium
-
None
-
None
The u/s CSIT generally runs this test in tell mode. As an experiment we ran this (and other tests) in ask mode and it failed.
What I see is:
- odl1 is the initial leader for the default-config shard
- the test removes the shard replica from odl1
- odl3 becomes the default-config shard leader
- odl2 receives a LeaderStateChanged event to the effect of (3)
- odl1 does NOT receive the LeaderStateChanged event (??)
- transactions that were in the pipeline on odl1 all fail and this message is omitted in the logs:
2018-08-01T12:18:19,503 | WARN | opendaylight-cluster-data-akka.actor.default-dispatcher-37 | LocalThreePhaseCommitCohort | 288 - org.opendaylight.controller.sal-distributed-datastore - 1.7.3.SNAPSHOT | Failed to prepare transaction member-1-datastore-config-fe-0-chn-10-txn-509-0 on backend
org.opendaylight.controller.cluster.datastore.exceptions.NoShardLeaderException: Could not process ready local transaction member-1-datastore-config-fe-0-chn-10-txn-509-0. Shard member-1-shard-default-config currently has no leader. Try again later.
- relates to
-
CONTROLLER-1786 Jolokia lookup says leader exists but karaf logs says no leader
- Resolved
-
OVSDB-434 br-int not created after failing over one controller in 3 node cluster
- Resolved
-
NETVIRT-1315 Troubleshooting Controller CSIT
- In Progress