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

Workspace is continuously restarted after start interruption #14567

Closed
mmorhun opened this issue Sep 17, 2019 · 0 comments · Fixed by #14728
Closed

Workspace is continuously restarted after start interruption #14567

mmorhun opened this issue Sep 17, 2019 · 0 comments · Fixed by #14728
Assignees
Labels
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. status/in-progress This issue has been taken by an engineer and is under active development.
Milestone

Comments

@mmorhun
Copy link
Contributor

mmorhun commented Sep 17, 2019

Describe the bug

This is nasty bug when a user cannot interrupt start of a workspace. The only way to stop it just wait until it fully started and only then stop it.

Che version

nightly

Steps to reproduce

  1. Start a workspace
  2. In a few second, while it is starting, click on Stop button
  3. Workspace start willbe interrupted and right after it, Che will try to start the same workspace again.

Expected behavior

Workspace start should be interrupted

Runtime

Minikube, Minishift
Che multiuser

Additional context

We had the same problem before but it was fixed and now appeared again.

@mmorhun mmorhun added kind/bug Outline of a bug - must adhere to the bug report template. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 17, 2019
@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. team/ide2 and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 17, 2019
@sunix sunix added this to the 7.3.0 milestone Sep 18, 2019
@akurinnoy akurinnoy self-assigned this Oct 1, 2019
@akurinnoy akurinnoy added the status/in-progress This issue has been taken by an engineer and is under active development. label Oct 1, 2019
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. severity/P1 Has a major impact to usage or development of the system. status/in-progress This issue has been taken by an engineer and is under active development.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants