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:

1. odl1 is the initial leader for the default-config shard
2. the test removes the shard replica from odl1
3. odl3 becomes the default-config shard leader
4. odl2 receives a LeaderStateChanged event to the effect of (3)
5. odl1 does NOT receive the LeaderStateChanged event (??)
6. 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.