Kontena Node loss doesn't result in change of state

[four43]

I terminated an instance that was running as a Kontena Node. After creating a new node and registering it with the cluster nothing happened. Kontena did not try and restart VPN, the registry, or services that were running on that host. Is this desired behavior? Kontena is still staging that the registry is up and running just fine, even though the host it is on is gone:

$ kontena service show registry
mygrid/registry:
  status: running
  stateful: yes
  scaling: 1
  image: kontena/registry:2.1
  dns: registry.mygrid.kontena.local
  affinity: 
    - node==ip-10-0-0-99
  cmd: 
  env: 
    - REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY=/registry
    - REGISTRY_HTTP_ADDR=0.0.0.0:80
  ports:
  volumes:
    - /registry
  volumes_from:
  links: 
  cap_add:
  cap_drop:
  containers:

That host is no longer in the cluster:

$ kontena node list
Name                           OS                                       Driver          Labels                         Status    
ip-10-0-0-166                  Ubuntu 14.04.2 LTS (3.13.0-48-generic)   aufs            -                              online 

[four43]

Whoops, this shouldn't be here. I got a 500 from GitHub while submitting, so I resubmitted. Closing! See #169