Theia terminal must report the error if request to machine-exec fails

[sleshchenko]

Describe the bug

From time to time it happens that Theia terminal is empty and there is no clue for an user what is the cause.
In my case, debugging shows that che-machine-exec fails to create exec with error:

message: "Get https://172.30.0.1:443/api/v1/namespaces/labs-infra/pods?fieldSelector=status.phase%3DRunning&labelSelector=che.workspace_id%3Dworkspacepvsrvhkshe46hw5g: http2: no cached connection was available"

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

there is no clear scenario how to reproduce it, but it should be easy to build custom che-machine-exec that always return error and face the same.

Expected behavior

Theia (terminal extension) reports the issue when it happens.

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
  • provide a full command that was used to deploy Eclipse Che (including the output)
  • provide an output of chectl version command
• OperatorHub
• I don't know

Environment

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

Eclipse Che Logs

Additional context

[andrewyuau]

I am getting the same issue, @sleshchenko did you manage to fix the terminal not coming up issue?

[sleshchenko]

@andrewyuau the cause may be different, this issue is just about exposing failed requests to a user.
Could you check the che-machine-exec container logs? If you don't manage to solve the issue you face, please register a new one.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.