Skip to content
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

local: use agent token to deregister services #9683

Merged
merged 1 commit into from
Feb 19, 2021

Conversation

dnephin
Copy link
Contributor

@dnephin dnephin commented Feb 1, 2021

Hopefully improves the issue from #9577 (#7669, #8078).

If an ACL token used to register a service is removed before the service then anti-entropy sync can fail to deregister the service. In those cases the local agent logs are filled with noise from these failures, and it never resolves itself.

Previously it would attempt to fall back to the "default" token, then to the anonymous token. With this change it will first fall back to the "agent" token, then "default", then finally the anonymous.
ref: https://www.consul.io/docs/agent/options#acl_tokens

The agent token seems more appropriate in this case, since this is an "internal operation", not something initiated by the user.

@dnephin dnephin added the theme/acls ACL and token generation label Feb 1, 2021
@dnephin dnephin requested review from mkeeler and a team February 1, 2021 23:12
@github-actions github-actions bot removed the theme/acls ACL and token generation label Feb 1, 2021
Copy link
Member

@hanshasselberg hanshasselberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dnephin
Copy link
Contributor Author

dnephin commented Feb 16, 2021

TODO: add changelog entry

When de-registering in anti-entropy sync, when there is no service or
check token.

The agent token will fall back to the default (aka user) token if no agent
token is set, so the existing behaviour still works, but it will prefer
the agent token over the user token if both are set.

ref: https://www.consul.io/docs/agent/options#acl_tokens

The agent token seems more approrpiate in this case, since this is an
"internal operation", not something initiated by the user.
@dnephin dnephin force-pushed the dnephin/fix-zombie-service-dereg branch from 6621e40 to 8a5163b Compare February 19, 2021 23:36
@vercel vercel bot temporarily deployed to Preview – consul February 19, 2021 23:36 Inactive
@vercel vercel bot temporarily deployed to Preview – consul-ui-staging February 19, 2021 23:36 Inactive
@dnephin dnephin merged commit b1d3c80 into master Feb 19, 2021
@dnephin dnephin deleted the dnephin/fix-zombie-service-dereg branch February 19, 2021 23:56
@hashicorp-ci
Copy link
Contributor

🍒 If backport labels were added before merging, cherry-picking will start automatically.

To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/330029.

hashicorp-ci pushed a commit that referenced this pull request Mar 5, 2021
local: use agent token to deregister services
dizzyup pushed a commit that referenced this pull request Apr 21, 2021
local: use agent token to deregister services
cmd-ntrf added a commit to ComputeCanada/puppet-magic_castle that referenced this pull request May 27, 2021
Fix issue with local: use agent token to deregister services
hashicorp/consul#9683
cmd-ntrf added a commit to ComputeCanada/puppet-magic_castle that referenced this pull request Jul 22, 2021
Fix issue with local: use agent token to deregister services
hashicorp/consul#9683
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants