consul service check on nomad windows client doesnt work
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 43
Description
#### Overview of the Issue
We have a nomad service running on windows host, with an http consul check, that doesn't seem to ever get checked.
Node checks are OK.
We tried to use a custom curl check, but that too was never triggered.
#### Reproduction Steps
Steps to reproduce this issue, eg:
```hcl
driver = "raw_exec"
service {
name = "{{print $service}}"
port = "REDACTED"
check {
name = "{{print $service}}-healthcheck"
type = "http"
port = "REDACTED"
path = "/health"
interval = "30s"
timeout = "25s"
}
check_restart {
limit = 5
grace = "270s"
ignore_warnings = false
}
}
```
### Consul info for both Client and Server
Client info
nomad
```ps1
PS C:\nomad> .\nomad.exe version
Nomad v0.11.3 (8918fc804a0c6758b6e3e9960e4eb2e605e38552)
```
consul
```shell
PS C:\consul> .\consul.exe info
agent:
check_monitors = 0
check_ttls = 0
checks = 0
services = 1
build:
prerelease =
revision = 7f3b5f34
version = 1.6.3
consul:
acl = disabled
known_servers = 3
server = false
runtime:
arch = amd64
cpu_count = 2
goroutines = 48
max_procs = 2
os = windows
version = go1.12.13
serf_lan:
coordinate_resets = 0
encrypted = true
event_queue = 0
event_time = 42
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 830
members = 12
query_queue = 0
query_time = 1
```
Server info
```shell
# nomad version
Nomad v0.11.2 (807cfebe90d56f9e5beec3e72936ebe86acc8ce3)
```
consul
```shell
agent:
check_monitors = 0
check_ttls = 0
checks = 2
services = 2
build:
prerelease =
revision = a42ded47
version = 1.5.3
consul:
acl = disabled
bootstrap = false
known_datacenters = 3
leader = false
leader_addr = REDACTED.129:8300
server = true
raft:
applied_index = 10154178
commit_index = 10154178
fsm_pending = 0
last_contact = 3.454052ms
last_log_index = 10154178
last_log_term = 124
last_snapshot_index = 10148993
last_snapshot_term = 124
latest_configuration = [{Suffrage:Voter ID:b1feb89a-b382-52de-6825-bd4fd5dea4cc Address:REDACTED.129:8300} {Suffrage:Voter ID:08d3e6be-e65d-dcfa-069b-84ff95732ea7 Address:REDACTED.158:8300} {Suffrage:Voter ID:24cac505-8465-913e-a9d6-7ce0e1fc224b Address:REDACTED.198:8300}]
latest_configuration_index = 1432601
num_peers = 2
protocol_version = 3
protocol_version_max = 3
protocol_version_min = 0
snapshot_version_max = 1
snapshot_version_min = 0
state = Follower
term = 124
runtime:
arch = amd64
cpu_count = 4
goroutines = 426
max_procs = 4
os = linux
version = go1.12.1
serf_lan:
coordinate_resets = 0
encrypted = true
event_queue = 0
event_time = 42
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 830
members = 12
query_queue = 0
query_time = 1
serf_wan:
coordinate_resets = 0
encrypted = true
event_queue = 0
event_time = 1
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 78
members = 9
query_queue = 0
query_time = 1
```
### Operating system and Environment details
infra is on AWS eu-west-1
nomad server is Ubuntu 16.04.6 LTS
consul server is on Ubuntu 18.04.3 LTS
nomad client is on Windows_Server-2019-English-Core-ContainersLatest-2020.07.15 (ami-0fc75deae31bee04f)


Contributor guide
Assessment
This issue has not been assessed yet.