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

Plugin Broker doesn't work on multi-user Che #11071

Closed
sleshchenko opened this issue Sep 5, 2018 · 0 comments
Closed

Plugin Broker doesn't work on multi-user Che #11071

sleshchenko opened this issue Sep 5, 2018 · 0 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template.

Comments

@sleshchenko
Copy link
Member

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

  1. Deploy Che with Plugin Registry configured.
  2. Create a workspace with configured plugins.
  3. 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.
    screenshot_20180905_112959
@sleshchenko 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
@l0rd l0rd mentioned this issue Sep 5, 2018
57 tasks
@l0rd l0rd mentioned this issue Sep 6, 2018
24 tasks
@sleshchenko sleshchenko self-assigned this Sep 6, 2018
@sleshchenko 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
@sleshchenko sleshchenko removed the status/in-progress This issue has been taken by an engineer and is under active development. label Sep 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

No branches or pull requests

2 participants