-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Fix cilium metrics list
: revert "prometheus/client_golang"
#19496
Conversation
Commit 3c6a77c2aca9cc5575f3e89b066e2af383f62b54 does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
3c6a77c
to
ff01139
Compare
Commit 3c6a77c2aca9cc5575f3e89b066e2af383f62b54 does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably makes sense to ignore github.com/prometheus/client_golang
in the dependabot config until a new version with a fix is released. So the bot won't attempt to update the dependency again.
Lines 9 to 18 in b79ebcf
ignore: | |
# using a cilium-specific fork | |
- dependency-name: "github.com/miekg/dns" | |
# k8s dependencies will be updated manually along with tests | |
- dependency-name: "k8s.io/*" | |
- dependency-name: "sigs.k8s.io/*" | |
# cloud provider SDKs are updated too frequently, update them manually | |
- dependency-name: "github.com/aliyun/alibaba-cloud-sdk-go" | |
- dependency-name: "github.com/aws/*" | |
- dependency-name: "github.com/Azure/*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While we're at it and given that dependabot ignores this dep for now, could we bump from v1.11.0 to v1.11.1 to pull in the security fix?
5302f24
to
db071b8
Compare
@rolinh Good point, done! |
db071b8
to
be197d4
Compare
/test Job 'Cilium-PR-K8s-GKE' hit: #17628 (95.15% similarity) |
be197d4
to
7315b93
Compare
/test Job 'Cilium-PR-K8s-1.23-kernel-net-next' hit: #18895 (93.74% similarity) |
7315b93
to
c82d92b
Compare
/test |
This reverts commit d8e3f28. --- See cilium#19425. Extra Go metrics were added to the Prometheus client, some having NaN values, breaking json marshaling on the server side of `cilium metrics list`: msg="Cilium API handler panicked" panic_message="json: unsupported value: NaN" url=/v1/metrics/ ... Signed-off-by: Timo Beckers <timo@isovalent.com>
Signed-off-by: Timo Beckers <timo@isovalent.com>
c82d92b
to
187f1c3
Compare
/test Job 'Cilium-PR-K8s-GKE' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment |
This seems like a straightforward revert, approvals are in. The CI runs below are hitting issues, the kafka one looks new to me but I don't understand how the PR could be related: https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/8303/ Please do consider filing issues or referencing existing issues if these are flakes we are not yet tracking. However, given this is resolving a known issue due to the dependency bump, and reverting back to the previous version should be safe, I think this is good to merge. |
This reverts commit d8e3f28.
Extra Go metrics were added to the Prometheus client, some having NaN values, breaking json marshaling on the server side of
cilium metrics list
:msg="Cilium API handler panicked" panic_message="json: unsupported value: NaN" url=/v1/metrics/ ...
Fixes: #19425