Leader leaving deregistered node, but not raft peer

[armon]

Node one: http://sprunge.us/YUNV
Node two: http://sprunge.us/jTWd
Node three: http://sprunge.us/AcSC

It appears that node 3 became leader, then attempted a leave. In the logs we can see:
"[INFO] consul: member 'three' left, deregistering"

So that the node was deregistered from the catalog, but was not removed as a Raft peer.

[armon]

Hint: This appears to happen when the leaving node is the old leader

[nelhage]

Pretty sure we're seeing this, too. Three-node consul 0.3.1 cluster.

The node in question was the leader; I executed a consul leave to trigger a graceful leave; It left and shut down, and then my process supervision immediately restarted it. At the end of the process, it had been flushed from the catalog but was still present in peer lists.