Push out new map before leaving cluster when rebalancing

Previously if the node running the orchestrator was being removed, we
could end up being left with an old map.

Change-Id: Ic84d654c38f009d6e849426ef89cf0cb335483f6
Reviewed-on: http://review.northscale.com:8080/809
Reviewed-by: Steve Yen <steve.yen@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

src/ns_orchestrator.erl

@@ -272,6 +272,8 @@ do_rebalance(Bucket, KeepNodes, EjectNodes, Map) ->
         ns_bucket:set_servers(Bucket, KeepNodes),
         ns_bucket:set_map(Bucket, Map5),
         update_progress(Bucket, AllNodes, 0.9),
+        %% Push out the config with the new map in case this node is being removed
+        ns_config_rep:push(),
         maybe_stop(),
         ns_cluster_membership:deactivate(EjectNodes),
         %% Leave myself last