Blocking writes on a tribe node creates a "blocks" tribe

[bodgit]

From the configuration a tribe node can block write operations with the following configuration:

tribe:
  blocks:
    write: true
  t1:
    cluster: ...

However when I do this, as well as getting the t1 tribe, I also end up with a blocks tribe that fails to find a cluster:

$ curl 'localhost:9200/_cluster/state/nodes?pretty'
...
    "rOnYeMT2QmSQAWVeNjCypg" : {
      "name" : "Kohl Harder Boulder Man/blocks",
      "transport_address" : "inet[/10.0.0.1:9302]",
      "attributes" : {
        "tribe.name" : "blocks",
        "client" : "true",
        "data" : "false"
      }
    },
...

[kimchy]

aye, this is a bug, will work on a fix