-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Health check removed when deregister not-linked service #5456
Comments
ShimmerGlass
pushed a commit
to ShimmerGlass/consul
that referenced
this issue
Mar 10, 2019
deregistration This guards against hashicorp#5456
vfrz
pushed a commit
to vfrz/consul
that referenced
this issue
Mar 10, 2019
deregistration This guards against hashicorp#5456
Script for easy reproducing (run # Register two service instances
for port in 31508 31226; do
jq --arg port $port -n '{
"Address": "127.0.0.1",
"Port": $port|tonumber,
"Check": {
"Interval": "5s",
"HTTP": ("http://localhost:"+$port+"/health-check")
},
"Name": "my-service",
"ID": ("my-service-"+$port)
}' | curl -XPUT localhost:8500/v1/agent/service/register -d@-
done
# Verify two checks exist (plus Consul's usual serfHealth check)
curl localhost:8500/v1/health/node/localhost
# Deregister *one* instance
consul services deregister -id my-service-31508
# Only Consul's serfHealth check remains
curl localhost:8500/v1/health/node/localhost |
ShimmerGlass
pushed a commit
to criteo-forks/consul
that referenced
this issue
Mar 12, 2019
deregistration This guards against hashicorp#5456
mkeeler
pushed a commit
that referenced
this issue
Mar 14, 2019
Fix my recently discovered issue described here: #5456
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview of the Issue
I have two service registered with one health check per service, when I deregister the first service, the health check of the second get deregistered but continue to check.
** Fix proposal PR: #5457 **
Reproduction Steps
/agent/checks
endpoint(8. After restarting Consul, Check 2 is appearing again)
Consul and environment info
Using Consul v1.4.3 on Windows 10 x64
Can't reproduce using v1.4.2, the bug was surely introduced with this commit: 2aac4d5
I'll update the issue alongside my research.
The text was updated successfully, but these errors were encountered: