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 fingerprint: eliminate spurious warning logs with Consul CE into release/1.7.x #19927

Conversation

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

Backport

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

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


Support for fingerprinting the Consul admin partition was added in #19485. But when the client fingerprints Consul CE, it gets a valid fingerprint and working Consul but with a warn-level log. Return "ok" from the partition extractor, but also ensure that we only add the Consul attribute if it actually has a value.

Fixes: #19756


Overview of commits

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/b-consul-partition-fingerprint/neatly-cheerful-alpaca branch from 5d0afdf to 85ff05b Compare February 9, 2024 13:19
@tgross tgross merged commit 5420dda into release/1.7.x Feb 9, 2024
19 of 20 checks passed
@tgross tgross deleted the backport/b-consul-partition-fingerprint/neatly-cheerful-alpaca branch February 9, 2024 13:48
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 20, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants