You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When filing a bug, please include the following headings if possible. Any example text in this template can be deleted.
Overview of the Issue
Consul can not re-define a config entry for a service once it's been written.
Reproduction Steps
I was using nomad to spin up the service, so:
Run a job which includes 1 task and includes a connect {} stanza with a consul sidecar.
Wait for the service to appear, write a config entry as follows:
Kind = "service-defaults"
Name = "redis"
Protocol = "http"
Realize that it's actually tcp and you should double check things before running your template jobs
Re-write the config entry
Kind = "service-defaults"
Name = "redis"
Protocol = "tcp"
>
$ consul config write /etc/consul.d/files/redis.hcl
Error writing config entry service-defaults/redis: Unexpected response code: 500 (service "redis" has protocol "tcp", which does not match defined listener protocol "http")
Try to delete the config entry via
$consul config delete -kind service-defaults -name redis
Error deleting config entry service-defaults/redis: Unexpected response code: 500 (service "redis" has protocol "tcp", which does not match defined listener protocol "http")
May 27 14:57:22 ip-10-0-1-7 consul: 2021-05-27T14:57:22.938Z [ERROR] agent.http: Request error: method=DELETE url=/v1/config/service-defaults/redis from=127.0.0.1:45328 error="service "redis" has protocol "tcp", which does not match defined listener protocol "http""
The text was updated successfully, but these errors were encountered:
truehhart
changed the title
Can't re-write config entry
Problems when re-writing service config-entry
May 27, 2021
When filing a bug, please include the following headings if possible. Any example text in this template can be deleted.
Overview of the Issue
Consul can not re-define a config entry for a service once it's been written.
Reproduction Steps
I was using nomad to spin up the service, so:
Consul info for both Client and Server
Client info
Server info
Operating system and Environment details
Log Fragments
The text was updated successfully, but these errors were encountered: