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

jaeger ui no data #178

Closed
luojianlong opened this issue Sep 8, 2023 · 1 comment
Closed

jaeger ui no data #178

luojianlong opened this issue Sep 8, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@luojianlong
Copy link

Steps to reproduce

jaeger ui page error: No trace results. Try another query.

kelemetry-informers container log error: level=error msg="query discovery API failed: unable to retrieve the complete list of server APIs: custom.metrics.k8s.io/v1beta1: the server is currently unable to handle the request" cluster=cluster1 mod=discovery

Expected behavior

No response

Actual behavior

No response

Kelemetry version

v0.2.4

Environment

No response

@luojianlong luojianlong added the bug Something isn't working label Sep 8, 2023
@SOF3
Copy link
Member

SOF3 commented Sep 8, 2023

Discovery API is returning error because custom metrics server was not cleanly uninstalled. You will notice the same problem with other controllers that use the Discovery API, e.g. your namespaces will be stuck at terminating because namespace controller cannot discover resources.

  • If you still need the custom metrics server, you can fix the installation; see https://stackoverflow.com/a/75266326/3990767
  • If you don't need it anymore, just uninstall it with kubectl delete apiservices v1beta1.custom.metrics.k8s.io.

See helm/helm#6361 for a similar issue.

@SOF3 SOF3 closed this as not planned Won't fix, can't repro, duplicate, stale Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants