nomad does not register HTTP tag for server in Consul #23384
Comments
|
Hi @BrianHicks! I wasn't able to reproduce what you're seeing on either 1.8.0 or the current tip of If you were to run the server with
Also, if you run the following command against one of the servers, what's the response body look like? nomad operator api '/v1/agent/self' | jq '.config.Consuls' |
|
How interesting! I don't see any such message when running in debug; here's the output: And here's the output of the command: [
{
"Addr": "127.0.0.1:8501",
"AllowUnauthenticated": true,
"Auth": "",
"AutoAdvertise": true,
"CAFile": "",
"CertFile": "",
"ChecksUseAdvertise": false,
"ClientAutoJoin": true,
"ClientFailuresBeforeCritical": 0,
"ClientFailuresBeforeWarning": 0,
"ClientHTTPCheckName": "Nomad Client HTTP Check",
"ClientServiceName": "nomad-client",
"EnableSSL": true,
"GRPCAddr": "",
"GRPCCAFile": "",
"KeyFile": "",
"Name": "default",
"Namespace": "",
"ServerAutoJoin": true,
"ServerFailuresBeforeCritical": 0,
"ServerFailuresBeforeWarning": 0,
"ServerHTTPCheckName": "Nomad Server HTTP Check",
"ServerRPCCheckName": "Nomad Server RPC Check",
"ServerSerfCheckName": "Nomad Server Serf Check",
"ServerServiceName": "nomad",
"ServiceIdentity": null,
"ServiceIdentityAuthMethod": "nomad-workloads",
"ShareSSL": null,
"Tags": null,
"TaskIdentity": null,
"TaskIdentityAuthMethod": "nomad-workloads",
"Timeout": 5000000000,
"Token": "<redacted>",
"VerifySSL": true
}
] |
|
Thanks @BrianHicks. I see that your Consul configuration doesn't have a I wouldn't expect to see any tags in that case, of course, but maybe the local agent has a cached version floating around from an earlier config? |
|
We didn't hear back on this so I'm going to close it out for now. If you have more information, we'll be happy to reopen. |
github-project-automation
bot
moved this from Triaging
to Done
in Nomad - Community Issues Triage
Nomad version
Operating system and Environment details
NixOS 24.05 running on Hetzner cloud VMs.
Issue
When
advertise.httpis set, Nomad is not registering ahttptag with Consul.rpcandserfare registered, though.(This is blocking me from scraping job metrics with Prometheus.)
Reproduction steps
Run Nomad using this config:
{ "acl": { "enabled": true }, "advertise": { "http": "{{ GetInterfaceIP \"enp7s0\" }}", "rpc": "{{ GetInterfaceIP \"enp7s0\" }}", "serf": "{{ GetInterfaceIP \"enp7s0\" }}" }, "consul": { "address": "127.0.0.1:8501", "ssl": true }, "data_dir": "/var/lib/nomad", "datacenter": "us-east", "log_level": "TRACE", "ports": { "http": 4646, "rpc": 4647, "serf": 4648 }, "server": { "bootstrap_expect": 1, "enabled": true }, "telemetry": { "collection_interval": "1s", "disable_hostname": true, "prometheus_metrics": true, "publish_allocation_metrics": true, "publish_node_metrics": true }, "tls": { "ca_file": "[SNIP]", "cert_file": "[SNIP]", "http": true, "key_file": "[SNIP]", "rpc": true, "verify_https_client": false, "verify_server_hostname": true }, "ui": { "enabled": true } }(Plus a side config I have not shared that sets
consul.token.)Expected Result
Nomad registers a
nomadservice withhttp,rpc, andserftags.Actual Result
Nomad only registers
rpcandserftags.Nomad Server logs (if appropriate)
The text was updated successfully, but these errors were encountered: