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

CloudShell workspace does not work in multiuser mode anymore #16060

Closed
1 of 3 tasks
sleshchenko opened this issue Feb 18, 2020 · 2 comments
Closed
1 of 3 tasks

CloudShell workspace does not work in multiuser mode anymore #16060

sleshchenko opened this issue Feb 18, 2020 · 2 comments
Assignees
Labels
area/machine-exec 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.

Comments

@sleshchenko
Copy link
Member

Describe the bug

CloudShell workspace does not work in multiuser mode anymore.
It's caused by the fact that JWTProxy now tries to connect to machine-exec via 127.0.0.1 but che-machine-exec is not configured in that way.

It's quite easy to prepare to fix for it by reconfiguring cloud-shell editor in plugin-registry as it's done for terminal plugin eclipse-che/che-plugin-registry#378 but then it won't work in SingleUser Che

JWTProxy is reconfigured in #15890

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

Just try to create and start a workspace with cloud-shell editor on MultiUser Che.

Runtime

Does not matter

Installation method

Does not matter

Environment

Does not matter

@sleshchenko sleshchenko added 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. area/machine-exec labels Feb 18, 2020
@sleshchenko
Copy link
Member Author

@rhopp Do you think we could create a small test in our selenium test-suite to prevent bugs in the future?

@tolusha tolusha mentioned this issue Feb 20, 2020
46 tasks
@AndrienkoAleksandr AndrienkoAleksandr self-assigned this Mar 4, 2020
@AndrienkoAleksandr AndrienkoAleksandr added the status/in-progress This issue has been taken by an engineer and is under active development. label Mar 4, 2020
@tolusha tolusha mentioned this issue Mar 5, 2020
45 tasks
@AndrienkoAleksandr AndrienkoAleksandr removed the status/in-progress This issue has been taken by an engineer and is under active development. label Mar 6, 2020
@AndrienkoAleksandr
Copy link
Contributor

Closed can't reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/machine-exec 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.
Projects
None yet
Development

No branches or pull requests

3 participants