failover of a dead server leads to disabled Rebalance button

using build 1.6.0a-57...

• join two servers A & B, and Rebalance them

• next, stop server B (/etc/init.d/northscale stop)

• in server A's web UI, it correctly lists server B as down.

• next, in server A's web UI, click the Fail Over button on server B's line

You get to a state where server B is listed a Failed Over / Pending Removal, but the Rebalance button is (incorrectly, imho) grey'ed out, so you can't get server B out of there.

(Also, server B is not listed in the Pending Rebalance tab, but that might be a JS thing.)

See: http://skitch.com/steveyen/djnjh/northscale-console-1.6.0a-206-gdd8a5cd

At this point: the curl/json output against server A looks like (showing "balanced" as true)...

1. curl http://10.1.3.35:8080/pools/default
   {"name":"default","nodes":[
   Unknown macro: {"clusterMembership"}

   ,

   Unknown macro: {"clusterMembership"}

   ],"buckets":

   {"uri":"/pools/default/buckets"}

   ,"controllers":{"addNode":

   {"uri":"/controller/addNode"}

   ,"rebalance":

   {"uri":"/controller/rebalance"}

   ,"failOver":

   {"uri":"/controller/failOver"}

   ,"reAddNode":

   {"uri":"/controller/reAddNode"}

   ,"ejectNode":

   {"uri":"/controller/ejectNode"}

   ,"testWorkload":{"uri":"/pools/default/controller/testWorkload"}},"balanced":true,"rebalanceStatus":"none","rebalanceProgressUri":"/pools/default/rebalanceProgress","stopRebalanceUri":"/controller/stopRebalance","stats":

   {"uri":"/pools/default/stats"}

   }