ACL token rotation causes check status inconsistency

### Edit(banks)

Note that the thread concludes a root cause that may not apply to this original issue related to ACLs. See https://github.com/hashicorp/consul/issues/4372#issuecomment-404529391 for a summary of the issue this represents now

----

Hi folks,
we run Consul 1.2.0 and encountered the following issue:
in the consul UI, when looking at some node Health check we see it is failing.

`curl http://localhost:8500/v1/health/node/ip-10-1-7-170

{
"Node": "ip-10-1-7-170",
"CheckID": "c49af2eedf67fdbf7135045051aad72c5f1d8a4c",
"Name": "Nomad Client HTTP Check",
"Status": "critical",
"Notes": "",
"Output": "",
"ServiceID": "_nomad-client-vsvkabaz4izafp6d5ejwyhrurtl2pdeq",
"ServiceName": "nomad-client",
"ServiceTags": [
"http"
],
"Definition": {},
"CreateIndex": 170787117,
"ModifyIndex": 170787117
},

`
after checking underlying API call /v1/agent/checks on the node the check is actually passing.

` curl http://localhost:8500/v1/agent/checks

"c49af2eedf67fdbf7135045051aad72c5f1d8a4c": {
"Node": "ip-10-1-7-170",
"CheckID": "c49af2eedf67fdbf7135045051aad72c5f1d8a4c",
"Name": "Nomad Client HTTP Check",
"Status": "passing",
"Notes": "",
"Output": "HTTP GET http://0.0.0.0:4646/v1/agent/health?type=client: 200 OK Output: {\"client\":{\"message\":\"ok\",\"ok\":true}}",
"ServiceID": "_nomad-client-vsvkabaz4izafp6d5ejwyhrurtl2pdeq",
"ServiceName": "nomad-client",
"ServiceTags": [
"http"
],
"Definition": {},
"CreateIndex": 0,
"ModifyIndex": 0
},
`