You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Plugin Broker doesn't work on multi-user Che.
The error that I faced during starting workspace with configured plugins - Plugin Broker failed to start because it didn't specify machine token while connecting to Che Server.
The scope of this issue is making Plugin Broker working on multi-user Che by using machine token and other possible issues which may occur on further phases of plugin broking.
Reproduction Steps
Deploy Che with Plugin Registry configured.
Create a workspace with configured plugins.
Try to start the workspace.
Expected: Workspace is started.
Actual: Workspace is failed because of timeout
Actually, Plugin Broker failed because of Che Server connection establishing error.
The text was updated successfully, but these errors were encountered:
sleshchenko
added
kind/bug
Outline of a bug - must adhere to the bug report template.
status/open-for-dev
An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
labels
Sep 5, 2018
sleshchenko
added
status/in-progress
This issue has been taken by an engineer and is under active development.
and removed
status/open-for-dev
An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
labels
Sep 6, 2018
Description
Plugin Broker doesn't work on multi-user Che.
The error that I faced during starting workspace with configured plugins - Plugin Broker failed to start because it didn't specify machine token while connecting to Che Server.
The scope of this issue is making Plugin Broker working on multi-user Che by using machine token and other possible issues which may occur on further phases of plugin broking.
Reproduction Steps
Expected: Workspace is started.
Actual: Workspace is failed because of
timeout
Actually, Plugin Broker failed because of Che Server connection establishing error.
The text was updated successfully, but these errors were encountered: