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

Backport of fix: stop peering delete routine on leader loss into release/1.15.x #17701

Conversation

hc-github-team-consul-core
Copy link
Contributor

Backport

This PR is auto-generated from #17483 to be assessed for backporting due to the inclusion of the label backport/1.15.

The below text is copied from the body of the original PR.


Description

This complements an enterprise PR that resolves an issue with namespaces but also affects the leader routine. When we lose leadership, we clean up the peering deferred deletion routine.

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/dans/fix-namespace-deletion-watch/sharply-trusting-heron branch from df69d18 to 76e8a2c Compare June 13, 2023 14:21
@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/dans/fix-namespace-deletion-watch/sharply-trusting-heron branch from fdc85cf to bedcec5 Compare June 13, 2023 14:21
Copy link

Choose a reason for hiding this comment

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

Auto approved Consul Bot automated PR

@hc-github-team-consul-core hc-github-team-consul-core merged commit 91f0d5b into release/1.15.x Jun 13, 2023
@hc-github-team-consul-core hc-github-team-consul-core deleted the backport/dans/fix-namespace-deletion-watch/sharply-trusting-heron branch June 13, 2023 14:44
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