[XDCR] cbrecovery thows out error NOT_MY_VBUCKET when running recovery to cluster that has failover nodes

Test run command

 ./testrunner -i ../ini/8-c-tools.ini -t cbRecoverytests.cbrecovery.restart_cbrecover_multiple_failover_swapout_reb_routine,items=300000,rdirection=bidirection,ctopology=chain,failover=destination,fail_count=2,add_count=2,max_verify=10000,when_step=create_bucket_when_recovery,extra_buckets=1

What test is doing:

• Install Couchbase Server 5.0.0-3506 on 8 Centos 7.x servers.
• Create a cluster A with 3 nodes
• Create a cluster B with 3 nodes
• Create default bucket on 2 cluster.
• Create bidirectional replication on 2 clusters.
• Load 300K items to default bucket on cluster A
• Wait for replication is done.
• Failover 2 nodes on cluster B.
• Add 2 nodes to cluster B
• Run command cbrecovery to recovery data from cluster A to cluster B
  cbrecovery failed to recover data from cluster A to cluster B.
  It throws out error "NOT_MY_VBUCKET" when running.

  2017-09-01 10:59:14,051: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne217478, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,051: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne144356, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,051: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne144424, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,051: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne146873, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,051: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne221178, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,051: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne147795, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,052: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne147177, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,052: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne147605, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,052: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne148926, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,052: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne222359, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,052: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne149022, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,052: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne149750, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,052: s1 warning: received NOT_MY_VBUCKET; perhaps the cluster is/was rebalancing; vbucket_id: 513, key: loadOne224069, spec: http://172.23.107.19:8091, host:port: 172.23.108.59:11210

  2017-09-01 10:59:14,052: s1 refreshing sink map:

Live cluster is available to debug at
Cluster A: 172.23.106.141
Cluster B: 172.23.107.19

I will collect logs and upload here soon.
I will find which build is the last success with this test.