-
Notifications
You must be signed in to change notification settings - Fork 2k
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
consul.partition fingerprint generates warning logs on CE #19756
Comments
@tgross Is there a way to disable this message through config currently if you're not using Consul? |
Unfortunately no. When you leave out the |
Okay, thanks. |
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
Will be fixed in #19923, planned for shipping in Nomad 1.7.5 |
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. |
The Consul fingerprint for Nomad CE generates a warning log after 1.7.3. I added support for fingerprinting the Consul admin partition in #19485 and tested it with combinations of Nomad CE/ENT and Consul CE/ENT. Unfortunately I apparently missed that if you fingerprint Consul CE from this code, you get a valid fingerprint and working Consul, but noise in your logs.
The "extractor" for the partition returns
"", false
, which the implementation treats as a warning. If we returned"", true
, we wouldn't get the warning but we'd get a useless fingerprint value ofconsul.partition = ""
which we don't want either. So we need to adjust the implementation to handle empty values differently too.Reported in #19485 (comment)
The text was updated successfully, but these errors were encountered: