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

Failed to fetch available workspaces and then failed to fetch list of namespaces errors on sandbox #22472

Closed
l0rd opened this issue Sep 5, 2023 · 5 comments
Closed

Failed to fetch available workspaces and then failed to fetch list of namespaces errors on sandbox #22472

l0rd opened this issue Sep 5, 2023 · 5 comments
Assignees
@dkwon17
Labels
area/gateway area/hosted-che 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

@l0rd
Copy link
Contributor

l0rd commented Sep 5, 2023 •
edited
Loading

Describe the bug

image image

Che version

7.73@latest

Steps to reproduce

open a workspace on sandbox

Expected behavior

should work

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Dev Sandbox (workspaces.openshift.com)

Eclipse Che Logs

No response

Additional context

No response
@l0rd l0rd added the kind/bug Outline of a bug - must adhere to the bug report template. label Sep 5, 2023
@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 Sep 5, 2023
@l0rd l0rd changed the title Failed to fetch list of namespaces Failed to fetch available workspaces and then failed to fetch list of namespaces errors on sandbox Sep 5, 2023
@dkwon17 dkwon17 added severity/P1 Has a major impact to usage or development of the system. area/hosted-che area/gateway and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 5, 2023
@dkwon17
Copy link
Contributor

dkwon17 commented Sep 5, 2023

This issue is likely caused by #22353 (comment)

@ibuziuk
Copy link
Member

ibuziuk commented Sep 7, 2023

@dkwon17 I remember we discussed also cm is not available, is it a separate problem?
Screenshot 2023-09-07 at 11 55 35

@ibuziuk
Copy link
Member

ibuziuk commented Sep 7, 2023

sorry, it is not relevant @tolusha I think it is related to eclipse-che/che-dashboard#912

@tolusha
Copy link
Contributor

tolusha commented Sep 7, 2023

It is needed to restart operator pod to pull a new operator image.

@dkwon17
Copy link
Contributor

dkwon17 commented Nov 2, 2023 •
edited
Loading

This issue is handled by dashboard request retries functionality:
eclipse-che/che-dashboard#942
eclipse-che/che-dashboard#946
eclipse-che/che-dashboard#958

I've verified the fix to be working on the dogfooding cluster

@dkwon17 dkwon17 closed this as completed Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dkwon17 dkwon17

Labels
area/gateway area/hosted-che 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
5 participants
@l0rd @ibuziuk @tolusha @che-bot @dkwon17