-
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
Che dashboard workspace is not loading on the UI #18499
Comments
Can you please provide more details on the ingress controller namespace |
It is working fine now, looks like an intermittent issue that came yesterday. Although, this issue is similar to - #18255. Not sure how it is working now, I haven't done any changes. did any one else faced this yesday as well ? or have you guys seen this error earlier ? |
I could not find any error in ingress logs though. |
Tried to reproduce on 2 different instances - I was not able to reproduce the problem. I'm not closing the issue, please provide more details when you are able to reproduce it again. |
Hello! I have the same error when creating a workspace. In the logs of the Theia container I saw the same errors as in @chopraaakash91, also I have an error in the JVT container that the connection was Hijacked. I am not very strong in the knowledge of Kubernetes, but can I provide any more information? |
Hello @myronV |
I'm using |
@myronV looks like you hit the same issue as described in #18552 (comment) |
All the same errors with |
Maybe @tolusha can help here. I'm not sure what was the solution for #18552 (comment) |
#18552 was closes as "Can't reproduce" @myronV @chopraaakash91 |
I am supposed that Eclipse Che has been installed using API urls are not set correctly CHE_API_INTERNAL=http://che-che.192.168.99.100.nip.io:8080/api
CHE_API=http://che-che.192.168.99.100.nip.io:8080/api
CHE_API_EXTERNAL=https://che-che.192.168.99.100.nip.io/api |
Hi! How I can do it? |
It is for
|
Oh, nice. Already is working. Thx for help |
@chopraaakash91 |
Fixed for (tested for both
|
I am trying to follow the contributing guide to start che-dashboard workspace - https://github.com/eclipse/che/blob/master/CONTRIBUTING.md#dashboard
I am using the below devfile to create a workspace for che-dashboard:
apiVersion: 1.0.0
metadata:
name: che-dashboard
projects:
source:
location: 'https://github.com/eclipse/che-dashboard.git'
type: git
components:
type: chePlugin
alias: typescript-plugin
endpoints:
public: 'true'
protocol: http
path: /
name: dashboard-dev-server
port: 3000
memoryLimit: 3Gi
type: dockerimage
image: 'quay.io/eclipse/che-dashboard-dev:nightly'
alias: dash-dev
commands:
actions:
type: exec
command: yarn build
component: dash-dev
actions:
type: exec
command: yarn
component: dash-dev
actions:
type: exec
command: 'npx gulp serve --server=${CHE_API_EXTERNAL%????}'
component: dash-dev
actions:
type: exec
command: yarn test
component: dash-dev
On the UI, I can see all logs are properly printed with all the images being pulled successfully and then it displays loading Runtime token and then it just keeps loading forever.
I can see all the pods are up and running in kubectl get pods.
Got the following error when checked the logs of theia container -
2020-12-01 12:12:07.640 root ERROR Security problem: Unable to configure separate webviews domain: Params: Error: Unable to get workspace containers. Cause: [object Object]
at CheServerWorkspaceServiceImpl. (/home/theia/node_modules/@eclipse-che/theia-remote-api/lib/node/che-server-workspace-service-impl.js:193:31)
at step (/home/theia/node_modules/@eclipse-che/theia-remote-api/lib/node/che-server-workspace-service-impl.js:62:23)
at Object.throw (/home/theia/node_modules/@eclipse-che/theia-remote-api/lib/node/che-server-workspace-service-impl.js:43:53)
at rejected (/home/theia/node_modules/@eclipse-che/theia-remote-api/lib/node/che-server-workspace-service-impl.js:35:65)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2020-12-01 12:12:07.641 root WARN Backend PluginApiContributionIntercepted.onStart is slow, took: 130096.1 ms
Also, in the chrome browser console, I see the following error - Error: TIMEOUT
at e._handleTimeout (https://static.developers.redhat.com/che/theia_artifacts/vendors.c8bdf28598a14f9b5776.js:365:8016)
at https://static.developers.redhat.com/che/theia_artifacts/vendors.c8bdf28598a14f9b5776.js:365:7896
The text was updated successfully, but these errors were encountered: