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
tested:
When removing the additional service stanzas from system type jobs and redeploy, the service registration leaks (not removed from Consul).
Reproduction steps
Deploy the job file below
Remove the following
- service {- name = "example-service-2"- port = "api"- }
Redeploy the job file
The service registration still in Consul, and will remain there even after the job is stopped and gc-ed.
Job file (if appropriate)
job"example-system-job" {
region="global"datacenters=["dc1"]
type="system"group"example-service-api-group" {
count=1network {
mode="bridge"portapi {}
}
service {
name="example-service-2"port="api"
}
service {
name="example-service"port="api"# this check seems have to be here, otherwise it will not trigger this bug.check {
type="http"port="api"path="/ready"interval="5s"timeout="1s"
}
}
task"example-fake" {
driver="docker"config {
image="nicholasjackson/fake-service:v0.12.0"
}
env {
LISTEN_ADDR="0.0.0.0:${NOMAD_PORT_api}"
}
}
}
}
The text was updated successfully, but these errors were encountered:
@fredwangwang Thank you for reporting, sorry you are running into this. I've tracked the issue down to the scheduler, when an inplace update is made (like removing or updating a service block) the allocations shared (group) ports are dropped. I've created #9735 to track and will have a fix soon.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
0.12.5
Operating system and Environment details
linux + Consul 1.8.3
Issue
tested:
When removing the additional service stanzas from
system
type jobs and redeploy, the service registration leaks (not removed from Consul).Reproduction steps
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: