Using CLI to add/rebalance leaves cluster with one active node and one dead node

With 1.6.0beta1rc7, When I use the rebalance cli command with the --server-add option, the command appears to work (in that it does not report any problems) but the result is an invalid cluster in which all the vbuckets are active on the original node but dead on the node being added.

[root@domU-12-31-36-00-45-D2 py]# python /opt/NorthScale/bin/cli/membase rebalance --cluster=10.253.11.144:8080 --server-add=10.253.30.47:8080
SUCCESS: server added..

[root@domU-12-31-36-00-45-D2 py]# python /opt/NorthScale/bin/cli/membase rebalance-status --cluster=10.253.11.144:8080
none
[root@domU-12-31-36-00-45-D2 py]# python /opt/NorthScale/bin/cli/membase server-list --cluster=10.253.11.144:8080
ns_1@10.253.11.144 healthy
ns_1@10.253.30.47 healthy
[root@domU-12-31-36-00-45-D2 py]# /opt/NorthScale/1.6.0beta1/bin/ep_engine/management/vbucketctl.py 10.253.11.144:11210 list
vbucket 0 active
vbucket 1 active
vbucket 10 active
..
vbucket 98 active
vbucket 99 active

[root@domU-12-31-36-00-45-D2 py]# /opt/NorthScale/1.6.0beta1/bin/ep_engine/management/vbucketctl.py 10.253.30.47:11210 list
vbucket 0 dead
vbucket 1 dead
vbucket 10 dead
...
vbucket 98 dead
vbucket 99 dead

Will attach logs