Workspace failed to start because of plugins installation process failed

[Ohrimenko1988]

Description

Some times workspace failed to start because of plugins installation process failed. This is especially true for CI jobs (on CI jobs error reproduces more often).

Reproduction Steps

• Deploy Che by "minikube" and "chectl"
• Go to "New Workspace" page
• Select "Che 7" stack
• Add java project
• Enable "Java Language Server" plugin
• Click on "Create and Open" button
• Wait until workspace is started

Expected behavior
Workspace is started and all selected plugins are installed

Observer behavior
Workspace failed to start

Attachments:
screenshot

text from screenshot:

Press F5 or click here to try again.
Starting Init Plugin Broker
Cleaning /plugins dir
Unified Che Plugin Broker
Starting Che common plugins processing
List of plugins and editors to install
- che-machine-exec-plugin:0.0.1 - Che Plug-in with che-machine-exec service to provide creation terminal or tasks for Eclipse CHE workspace machines.
- org.eclipse.che.vscode-redhat.java:0.38.0 - Java Linting, Intellisense, formatting, refactoring, Maven/Gradle support and more...
- org.eclipse.che.editor.theia:1.0.0 - Eclipse Theia
Starting VS Code plugins processing
Downloading VS Code extension for plugin 'org.eclipse.che.vscode-redhat.java:0.38.0'
Starting Theia plugins processing
stream error: stream ID 1; HTTP_1_1_REQUIRED
Error: Failed to run the workspace: "Plugins installation process failed. Error: Plugin broking process for workspace workspacewirxn0fza1vyf9ey failed with error: stream error: stream ID 1; HTTP_1_1_REQUIRED"

che server logs:
logs-from-che-in-che-655bbd79d4-kk4dd.txt

theia ide logs:
logs-from-theia-ide-in-workspacezmwud1a6w61z12qb.ws-86dbd8b6c6-wntqd.txt

plugins sidecar logs:
logs-from-pluginsidecarpkqjxn-in-workspacezmwud1a6w61z12qb.ws-86dbd8b6c6-wntqd.txt

OS and version:

• Che 7.0.0-beta-3.0 ;
• minikube v0.28.0 ;
• chectl 0.0.2 linux-x64 node-v10.4.1

[l0rd]

This doesn't look like a team/languages issue but more a team/ide2 or team/osio issue because it involves brokering and Theia plugin loading.

@tsmaeder @ibuziuk @evidolob can you help triaging this issue?

[ibuziuk]

Taken into next sprint by Che OSIO team - redhat-developer/rh-che#1356

[ibuziuk]

@garagatyi maybe you have some ideas about that issue - stream error: stream ID 1; HTTP_1_1_REQUIRED" ?

[garagatyi]

Might be somehow related with rate limiting. It will be tricky to fix since there is no way to reproduce it as far as I understand. @Ohrimenko1988 Am I correct that you don't know how to reproduce it?

[Ohrimenko1988]

@garagatyi Yes, it is a random reproduced issue

[ibuziuk]

@Ohrimenko1988 @vkuznyetsov without a strong reproducer we can not do much atm ¯_(ツ)_/¯

[Ohrimenko1988]

@ibuziuk Maybe I can help you with this? What additional information do you need? I may catch it on CI jobs.

[ibuziuk]

@Ohrimenko1988 well, we need a strong reproducer in order to consistently repro locally

[Ohrimenko1988]

Anyway, bug is still actual.

[ibuziuk]

@Ohrimenko1988 so, no steps to repro locally?

[Ohrimenko1988]

Unfortunately, no updates

[ibuziuk]

@Ohrimenko1988 is this issue still reproducible ?

[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.