Can not start a terminal

[RomanNikitenko]

Describe the bug

Sometimes I can not start a terminal.
I can not reproduce it permanently.
Please see a screenshot.

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

1. Create and start a workspace from dashboard
2. Go to Terminal -> Open Terminal in specific container

Expected behavior: list of containers is displayed to select the corresponding container for starting a terminal.

Actual behavior: a terminal widget is displayed, but a terminal is not started. There is an error in browser console.

Uncaught (in promise) Error: Failed to start terminal. Cause: Error: Couldn't parse params
    at n.<anonymous> (theia.0fdc8ed05bd4da17210d.js:1)
    at theia.0fdc8ed05bd4da17210d.js:1
    at Object.throw (theia.0fdc8ed05bd4da17210d.js:1)
    at s (theia.0fdc8ed05bd4da17210d.js:1)

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

Screenshots

Installation method

• chectl
• che-operator
• minishift-addon
• I don't know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: please specify

[metlos]

Possibly related to #15870 ?

[sparkoo]

@RomanNikitenko can you please write here the error message from the browser console you've mentioned ?

[RomanNikitenko]

@sparkoo

can you please write here the error message from the browser console you've mentioned ?

Done!

I'm not sure, but maybe the error comes from machine-exec https://github.com/eclipse/che-machine-exec/blob/5c8d22d2cf59c3b857ca8120271659f64c726883/vendor/github.com/eclipse/che-go-jsonrpc/tunnel.go#L411

[tolusha]

@RomanNikitenko
Do you still reproduce the issue?

[RomanNikitenko]

@tolusha
I tried a few times today and could not reproduce it.

So, maybe the problem is gone...
Please feel free to close the issue if you can not reproduce it.

[vparfonov]

Reproduced on my side, with OSD and che-theia:next

Error: Failed to start terminal. Cause: Error: Couldn't parse params

UPD: after refresh page opened early terminal initialized, but new one still don't

[vitaliy-guliy]

My terminal become not working after appearing the message, that the new process is listening 4444 port.

[amisevsk]

My terminal become not working after appearing the message, that the new process is listening 4444 port.

That indicates that the machine exec container restarted -- do you see any restarts in the workspace pod?

[vitaliy-guliy]

I didn't check the logs, will do it next time when I face the error.

[AndrienkoAleksandr]

OK, Stable steps to reproduce:

1. Open terminal widget.
2. Launch some not endless che task.
3. When task done click on the task widget and type some character.
4. Await few seconds. Select terminal widget and try to type something.

Actual result: opened terminal stopped work.

@RomanNikitenko thanks for reporting issue. @vitaliy-guliy thanks a lot too, your screenshot is relevant too.

@vparfonov Sorry, about this one #16601 (comment) I am not sure. I didn't faced with such behavior.