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

Che dashboard workspace is not loading on the UI #18499

Closed
chopraaakash91 opened this issue Dec 1, 2020 · 17 comments
Closed

Che dashboard workspace is not loading on the UI #18499

chopraaakash91 opened this issue Dec 1, 2020 · 17 comments
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@chopraaakash91
Copy link

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:

  • name: che-dashboard
    source:
    location: 'https://github.com/eclipse/che-dashboard.git'
    type: git
    components:
  • id: che-incubator/typescript/latest
    type: chePlugin
    alias: typescript-plugin
  • mountSources: true
    endpoints:
    • attributes:
      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:
  • name: '[UD] build'
    actions:
    • workdir: /projects/che-dashboard
      type: exec
      command: yarn build
      component: dash-dev
  • name: '[UD] install dependencies'
    actions:
    • workdir: /projects/che-dashboard
      type: exec
      command: yarn
      component: dash-dev
  • name: '[UD] start dev-server'
    actions:
    • workdir: /projects/che-dashboard
      type: exec
      command: 'npx gulp serve --server=${CHE_API_EXTERNAL%????}'
      component: dash-dev
  • name: '[UD] test'
    actions:
    • workdir: /projects/che-dashboard
      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

@chopraaakash91 chopraaakash91 added the kind/bug Outline of a bug - must adhere to the bug report template. label Dec 1, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Dec 1, 2020
@veeramanikandanvv
Copy link

Can you please provide more details on the ingress controller namespace

@chopraaakash91
Copy link
Author

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 ?

@chopraaakash91
Copy link
Author

I could not find any error in ingress logs though.

@RomanNikitenko
Copy link
Member

RomanNikitenko commented Dec 2, 2020

It is working fine now, looks like an intermittent issue that came yesterday.

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.

@RomanNikitenko RomanNikitenko added status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 2, 2020
@myronV
Copy link

myronV commented Dec 8, 2020

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?

@azatsarynnyy
Copy link
Member

Hello @myronV
what version of Che Server and Che-Theia you're using?
Recently we've met a similar issue that was caused by incompatible versions of different components.
For example #18552 (comment)

@myronV
Copy link

myronV commented Dec 8, 2020

Hello @myronV
what version of Che Server and Che-Theia you're using?
Recently we've met a similar issue that was caused by incompatible versions of different components.
For example #18552 (comment)

I'm using
Eclipse Che CLI
VERSION
chectl/0.0.20201203-next.d87017f wsl-x64 node-v10.23.0
Eclipse Che Version : 7.23.0-SNAPSHOT
and Theia-ide:latest

@azatsarynnyy
Copy link
Member

@myronV looks like you hit the same issue as described in #18552 (comment)
Try switching to che-theia:next

@myronV
Copy link

myronV commented Dec 8, 2020

@myronV looks like you hit the same issue as described in #18552 (comment)
Try switching to che-theia:next

All the same errors with che-theia:next
Also, I have errors in the web-browser, about loading resources timeout
image

@azatsarynnyy
Copy link
Member

Maybe @tolusha can help here. I'm not sure what was the solution for #18552 (comment)

@tolusha
Copy link
Contributor

tolusha commented Dec 9, 2020

#18552 was closes as "Can't reproduce"

@myronV @chopraaakash91
Try to update eclipse-che custom resource and set
spec.server.useInternalClusterSVCNames: false

@tolusha
Copy link
Contributor

tolusha commented Dec 9, 2020

I am supposed that Eclipse Che has been installed using --installer helm .
Could you confirm that ?

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

@tolusha tolusha mentioned this issue Dec 9, 2020
12 tasks
@myronV
Copy link

myronV commented Dec 9, 2020

Try to update eclipse-che custom resource and set
spec.server.useInternalClusterSVCNames: false

Hi! How I can do it?
And yes, I used --installer helm for deploying Eclipse Che.

@tolusha
Copy link
Contributor

tolusha commented Dec 9, 2020

spec.server.useInternalClusterSVCNames: false

It is for --installer operator.
Meanwhile please use the latest stable version of chectl

  1. chectl update stable
  2. checlt server:deploy...

@myronV
Copy link

myronV commented Dec 9, 2020

It is for --installer operator.

Oh, nice. Already is working. Thx for help

@tolusha
Copy link
Contributor

tolusha commented Dec 9, 2020

@chopraaakash91
could you provide more details about your cases?
Could you provide checlt command line you used ?

@tolusha
Copy link
Contributor

tolusha commented Dec 10, 2020

Fixed for (tested for both --installer helm and --installer operator)

$ chectl version
chectl/0.0.20201210-next.0af053a linux-x64 node-v10.23.0

@tolusha tolusha closed this as completed Dec 10, 2020
@tolusha tolusha added this to the 7.23 milestone Dec 10, 2020
@tolusha tolusha added area/install Issues related to installation, including offline/air gap and initial setup severity/P1 Has a major impact to usage or development of the system. and removed status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Dec 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

7 participants