Successfully returning health for a node not list as a member

[Gregorio Di Stefano]

Hi, 

We recently hit an oddity in consul, where we were able to query the health of a node, and get a valid response, while the node was not listed as a member.

The node was turned off for a little over an hour, and we would expect it to state it was in `left` state, but, in reality, it's not listed.

Previously, we don't believe to have seen this behavior, and are wondering if we hit a bug.

This is consul 1.6.2.

Thanks,

Greg

[schri...@hashicorp.com]

Howdy Greg,

Thank you so much for bringing this to our attention! A couple questions to solidify my understanding:

Is the agent that is showing this behavior a server or a client? Are you able to consistently reproduce this issue? Can you provide replication steps, your consul config for your servers, relevant log snippets and `consul member` output?

I’m sorry to hear you’re coming across an unexpected behavior. I hope we can figure this out soon :)

- Sarah