Describe the bug
When closing the IDE one can "Close and Stop". It would not stop the workspace though. You end up having a running workspace that you cannot connect to any more.
Che version
7.109@latest
Steps to reproduce
- ASSERT: have a Jetbrains IDE (Ultimate, etc.) running.
- EXEC: quit the IDE
- ASSERT: you get a dialog where you can "Close and Stop"
- EXEC: click "Close and Stop"
- EXEC: verify if your workspace is still running (either in dashboard or in gateway)
Result:
The workspace is still running, it wasn't stopped.
Furthermore you cannot connect to the workspace any more.
Behind the scenes one can see that the remote-dev-server process was killed.
Expected behavior
The workspace should be stopped.
Runtime
OpenShift
Screenshots
No response
Installation method
other (please specify in additional context)
Environment
macOS
Eclipse Che Logs
Additional context
No response
Describe the bug
When closing the IDE one can "Close and Stop". It would not stop the workspace though. You end up having a running workspace that you cannot connect to any more.
Che version
7.109@latest
Steps to reproduce
Result:
The workspace is still running, it wasn't stopped.
Furthermore you cannot connect to the workspace any more.
Behind the scenes one can see that the
remote-dev-serverprocess was killed.Expected behavior
The workspace should be stopped.
Runtime
OpenShift
Screenshots
No response
Installation method
other (please specify in additional context)
Environment
macOS
Eclipse Che Logs
Additional context
No response