rebalancing after failing over a node which was down during a previous rebalance causes rebalance failure with bad replicators

the user noticed that memcached was down in one of the nodes.
they attempted to rebalance out the node instead of doing a failover

since memcached was down first rebalance attempt failed with wait_for_memcached error

then they failed over the node and started another rebalance.
second rebalance failed after an hour with this error :

2011-11-16 01:49:44.838 ns_rebalancer:2:info:message(ns_1@172.30.1.32) - Bad replicators after rebalance:
Missing = [

{'ns_1@172.30.1.33','ns_1@172.30.1.32',2}

,

{'ns_1@172.30.1.33','ns_1@172.30.1.32',3}

,
logs :
http://www.reptiles.org/~jim/case1318b.zip