Retrieval of Bridge and Port fails from Operational Store in csit test

In csit ovsdb 3 node cluster test, on 29 Jan 2016 with the distribution

"distribution-karaf-0.4.0-20160129.143739-3756.zip", I could able to retrieve the data(bridge and port) from the operational store successfully.
Here goes the releng log for reference [1]

[1] https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-verify-3node-clustering/133/

Today (01 Feb 2016) with the latest distribution "distribution-karaf-0.4.0-20160201.000357-3821.zip" in integration, I could see many tests fails which are retrieving data (bridge and port) from operational datastore.
Log reference for the above observation [2]

[2] https://jenkins.opendaylight.org/sandbox/job/ovsdb-csit-3node-clustering-only-beryllium/10/robot/report/log.html

In Contoller1 logs, i see the below exception:

2016-02-01 11:09:07,629 | WARN | n-invoker-impl-0 | TransactionInvokerImpl | 159 - org.opendaylight.ovsdb.southbound-impl - 1.2.1.SNAPSHOT | Exception invoking Transaction:
java.lang.IllegalStateException: Previous transaction member-1-chn-1-txn-2 is not ready yet
at org.opendaylight.controller.cluster.datastore.TransactionChainProxy$Allocated.checkReady(TransactionChainProxy.java:85)[139:org.opendaylight.controller.sal-distributed-datastore:1.3.0.SNAPSHOT]

In Controller2 logs, there was no much exception.

In Controller3 logs, i see the below exception:

ReadFailedException{message=Error executeRead ReadData for path /(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[

{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=ovsdb:1}

]/node/node[

{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)node-id=ovsdb://uuid/a96ec4e2-c457-4a2c-963c-1e6300210032}

], errorList=[RpcError [message=Error executeRead ReadData for path /(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[

{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=ovsdb:1}

]/node/node[

{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)node-id=ovsdb://uuid/a96ec4e2-c457-4a2c-963c-1e6300210032}

], severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, cause=org.opendaylight.controller.md.sal.common.api.data.DataStoreUnavailableException: Shard member-3-shard-topology-operational currently has no leader. Try again later.]]}

Added the 3 controllers logs url for full trace reference.

https://jenkins.opendaylight.org/sandbox/job/ovsdb-csit-3node-clustering-only-beryllium/10/artifact/odl1_karaf.log
https://jenkins.opendaylight.org/sandbox/job/ovsdb-csit-3node-clustering-only-beryllium/10/artifact/odl2_karaf.log
https://jenkins.opendaylight.org/sandbox/job/ovsdb-csit-3node-clustering-only-beryllium/10/artifact/odl3_karaf.log