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.

Sign up for GitHub

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

Jump to bottom

Websocket connection to the dashboard backend is closed #20898

Closed
Tracked by #20874
akurinnoy opened this issue Dec 7, 2021 · 1 comment
Closed
Tracked by #20874

Websocket connection to the dashboard backend is closed #20898

akurinnoy opened this issue Dec 7, 2021 · 1 comment
Assignees
@sparkoo
Labels
area/dashboard 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.

Comments

@akurinnoy
Copy link
Contributor

akurinnoy commented Dec 7, 2021 •
edited
Loading

Describe the bug

The Dashboard frontend can't establish the websocket connection to the Dashboard backend.

Che version

next (development version)

Steps to reproduce

  1. Deploy Eclipse Che with devworkspaces engine enabled
chectl server:deploy -p minikube --workspace-engine=dev-workspace --che-operator-cr-patch-yaml=patch.yaml
patch.yaml 
spec:
auth:
  updateAdminPassword: false
devWorkspace:
  enabled: true
server:
  cheImagePullPolicy: Always
  dashboardImagePullPolicy: Always
  customCheProperties:
    CHE_INFRA_KUBERNETES_ENABLE__UNSUPPORTED__K8S: "true"
k8s:
  singleHostExposureType: 'gateway'
  1. Go to the Dashboard
  2. And open JS console

Expected behavior

The websocket connection between dashboard frontend and backend is established.

Runtime

minikube

Screenshots

Screenshot 2021-12-07 at 18 07 29

Installation method

chectl/next

Environment

macOS

Eclipse Che Logs

No response

Additional context

No response
@akurinnoy akurinnoy added kind/bug Outline of a bug - must adhere to the bug report template. area/dashboard labels Dec 7, 2021
@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 7, 2021
@sparkoo sparkoo added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 8, 2021
@skabashnyuk skabashnyuk mentioned this issue Dec 9, 2021
Closed
13 tasks
@sparkoo sparkoo mentioned this issue Dec 9, 2021
Merged
11 tasks
@sparkoo
Copy link
Member

sparkoo commented Dec 9, 2021

fixed by eclipse-che/che-operator#1242

@sparkoo sparkoo closed this as completed Dec 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sparkoo sparkoo

Labels
area/dashboard 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
Milestone
No milestone
Development

No branches or pull requests
4 participants
@sparkoo @skabashnyuk @akurinnoy @che-bot