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

Grafana dashboard error #935

Closed
xhejtman opened this issue Jun 14, 2021 · 9 comments
Closed

Grafana dashboard error #935

xhejtman opened this issue Jun 14, 2021 · 9 comments
Labels
bug Something isn't working stale

Comments

@xhejtman
Copy link

xhejtman commented Jun 14, 2021

Describe the bug
I have bacically default helm installation. if I click on Namespaces -> Containers -> Dashboard, I can see the following error. Is it misconfiguration or a bug?

error

gz#399

@xhejtman xhejtman added the bug Something isn't working label Jun 14, 2021
@kbrwn
Copy link
Contributor

kbrwn commented Jun 14, 2021

@xhejtman this should be fixed in an upcoming kubecost release. You can test out a release candidate with the change if you'd like.

Release Notes: https://github.com/kubecost/cost-analyzer-helm-chart/releases/tag/v1.82.0-rc.0

Upgrade to RC commands:

$ helm repo update
$ helm upgrade kubecost kubecost/cost-analyzer --namespace kubecost -f values.yaml --devel

@kbrwn
Copy link
Contributor

kbrwn commented Jun 24, 2021

@xhejtman v1.82.0 is officially out: https://github.com/kubecost/cost-analyzer-helm-chart/releases/tag/v1.82.0

Please let us know if you are still having this issue after upgrading.

@xhejtman
Copy link
Author

hello, it seems that I am still having the issue in 1.82.0.

@AjayTripathy
Copy link
Contributor

Thanks for reporting this @xhejtman . The upgrade does not restart grafana-- you may need to manually restart it for the change to take effect.

@xhejtman
Copy link
Author

I redeployed grafana and I am still getting the error.

@AjayTripathy
Copy link
Contributor

Hi @xhejtman I do see the red error, but the graphs still appear readable for me and the error disappears after a few seconds-- is that also what's happening for you?

@xhejtman
Copy link
Author

Yes, this is what I'm seeing as well. The error disappears after a few seconds. So not a real bug but could be fixed ;)

@dwbrown2
Copy link
Contributor

dwbrown2 commented Aug 8, 2021

This is a function of the cluster variable missing and should not impact data.

@Adam-Stack-PM
Copy link

This issue has been marked as stale because it has not had recent activity. It will be closed if no further action occurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

5 participants