-
Notifications
You must be signed in to change notification settings - Fork 1.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
Failed to open Eclipse Che Dashboard on minikube v1.25.1 with DevWorkspace enabled #20984
Comments
For me, this happened with Che 7.41.1 on minikube v1.24.0, Kubernetes v1.22.3, Docker 20.10.8, chectl 7.41.1, kubectl (client:v1.23.1/server:v1.22.3). |
7.41.1 works fine |
hmm I've quickly looked at this, I can reproduce, but I don't know what's wrong. Token looks ok, permissions looks ok. I can't get the secret even if I try to use token with |
Which version minikube did you use for testing?
|
I have v1.25.0 I would suspect this patch eclipse-che/che-operator#1291. Can you test before and after? Or test stable version if it works ok? I think it's something with mismatching oidc configuration. client_id, secret, claim or something like that does not match kubernetes and Che configurations |
Can't reproduce after switching to minikube v1.24.0 and cleanin up old resources |
@tolusha I am reproducing it on a fresh minikube v1.25.1. What do you mean with "cleaning up old resources"? |
It works well for v1.24.0
I mean I will reopen to adopt to v1.25.x |
Moving to 7.44 as 7.43 has been released. |
I've been having this issue with clusters created in AWS EKS. Verified that the Dex installation is correct. It creates the namespace with the user name but then fails while checking for the Secret. I've given ClusterAdmin to all forms of claims from Dex and its clearly not using any of them. aws eks 1.21, dex 2.30.0, che 7.43.0, using che operator, and dev-workspace. |
lsb_release -a kubectl version chectl server:status |
We have to wait minikube v1.26.0 to test. kubernetes/minikube#13543 |
@tolusha
When I go to http://192.168.49.2.nip.io/dashboard/ on chrome, nothing is loading up |
yes, v1.24.0 works fine. |
@tolusha For minikube v1.24.0, the output shows deploy has completed successfully, but when I go to this https://192.168.49.2.nip.io/dashboard/ |
hmm. It works fine on my side |
@tolusha here are the logs, unable to load the dashboard
|
Describe the bug
Failed to open
Che version
next (development version)
Steps to reproduce
chectl update next
chectl server:deploy --platform minikube
chectl dashboard:open
Dashboard is not opened. Che server logs contains stacktrace.
Expected behavior
Dashboard is opened
Runtime
minikube
Screenshots
No response
Installation method
chectl/next
Environment
Linux
Eclipse Che Logs
The text was updated successfully, but these errors were encountered: