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

Deleting a not supported workspace breaks dashboard in OpenShift #10544

Closed
amisevsk opened this issue Jul 25, 2018 · 3 comments · Fixed by #10716
Closed

Deleting a not supported workspace breaks dashboard in OpenShift #10544

amisevsk opened this issue Jul 25, 2018 · 3 comments · Fixed by #10716
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template.

Comments

@amisevsk
Copy link
Contributor

Description

If you create a workspace that is not supported in a particular spin of Che and then delete it, the workspaces tab fails to populate with error Failed to retrieve workspace wksp-o078 data. Reason: Workspace with id 'workspacenn25oh2umzhkbgt9' doesn't exist until the page is refreshed. On the dashboard tab the deleted workspace is still listed.

Reproduction Steps

  1. Deploy current snapshot of Che on minishift
  2. Create Java-MySQL workspace, choose "Edit" option (or click top "Create" button)
  3. See that this workspace stack is not supported, delete workspace
  4. Che redirects to workspaces tab, which fails to load any workspaces.
  5. Dashboard tab still lists deleted workspace

OS and version:

Che 6.9.0-SNAPSHOT (current master branch)
minishift v1.21.0+a8c8b37
oc v3.9.0+191fece
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://192.168.42.148:8443
openshift v3.9.0+46ff3a0-18
kubernetes v1.9.1+a0ce1bc657
@amisevsk amisevsk added the kind/bug Outline of a bug - must adhere to the bug report template. label Jul 25, 2018
@amisevsk
Copy link
Contributor Author

Note: this is a temporary problem, refreshing the page clears up the error and it seems as though the workspace is deleted correctly. It's just suboptimal user experience.

@garagatyi
Copy link

@ashumilova FYI

@garagatyi
Copy link

This issue is probably caused by this PR which removes validation of workspace environment on workspace creation and leave it only on workspace start.

@akurinnoy akurinnoy self-assigned this Aug 9, 2018
@akurinnoy akurinnoy added sprint/current status/in-progress This issue has been taken by an engineer and is under active development. and removed sprint/next labels Aug 9, 2018
@ashumilova ashumilova removed sprint/current status/in-progress This issue has been taken by an engineer and is under active development. labels Aug 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants