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

It is not possible to start a terminal when workspace started from a devfile from the registry.devfile.io #22524

Closed
tolusha opened this issue Sep 18, 2023 · 1 comment · Fixed by che-incubator/che-code#284
Assignees
Labels
area/editors 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. team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs.

Comments

@tolusha
Copy link
Contributor

tolusha commented Sep 18, 2023

Describe the bug

It is not possible to start a terminal when workspace started from a devfile from the registry.devfile.io

Che version

next (development version)

Steps to reproduce

  1. Deploy Eclipse Che on OpenShift
  2. Configure external devfile registry https://registry.devfile.io
oc patch checluster/eclipse-che --patch '{"spec": {"components": {"devfileRegistry": {"disableInternalRegistry": true, "externalDevfileRegistries": [{"url": "'https://registry.devfile.io'"}]}}}}' --type=merge -n eclipse-che
  1. Start a workspace
  2. Start a terminal
    screenshot-eclipse-che apps ci-ln-zpry0jk-76ef8 aws-2 ci openshift org-2023 09 18-13_57_44

It is worth to note, that New terminal (Select a container) command works fine.

Expected behavior

Terminal successfully started.

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response

@tolusha tolusha added kind/bug Outline of a bug - must adhere to the bug report template. area/editors team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs. labels Sep 18, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 18, 2023
@l0rd
Copy link
Contributor

l0rd commented Sep 19, 2023

Included in #20251

@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 19, 2023
@l0rd l0rd moved this to 📅 Planned in Eclipse Che Team B Backlog Oct 2, 2023
@amisevsk amisevsk self-assigned this Oct 2, 2023
@amisevsk amisevsk moved this from 📅 Planned for this Sprint to 🚧 In Progress in Eclipse Che Team B Backlog Oct 11, 2023
@amisevsk amisevsk moved this from 🚧 In Progress to Ready for Review in Eclipse Che Team B Backlog Oct 11, 2023
@github-project-automation github-project-automation bot moved this from Ready for Review to ✅ Done in Eclipse Che Team B Backlog Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/editors 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. team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants