Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

che-plugin-registry devfile fails on workspaces.openshift.com (shellcheck plugin not found)

See original GitHub issue

Steps to reproduce - https://workspaces.openshift.com/#https://github.com/eclipse-che/che-plugin-registry

Add eth0 [10.128.5.93/23]

Pulling image "registry.redhat.io/codeready-workspaces/pluginbroker-metadata-rhel8@sha256:cd977a7e55dff0d478be81762db17dad3e9daf2cc8f80d168f6e3adcccca3986"

Successfully pulled image "registry.redhat.io/codeready-workspaces/pluginbroker-metadata-rhel8@sha256:cd977a7e55dff0d478be81762db17dad3e9daf2cc8f80d168f6e3adcccca3986" in 1.095152845s

Created container pluginbroker-metadata-rhel8-cd977a7e55

Started container pluginbroker-metadata-rhel8-cd977a7e55

Starting plugin metadata broker

Failed to download plugin meta: failed to fetch plugin meta.yaml from URL 'https://codeready-codeready-workspaces-operator.apps.sandbox.x8i5.p1.openshiftapps.com/plugin-registry/v3/plugins/timonwong/shellcheck/latest/meta.yaml': Downloading https://codeready-codeready-workspaces-operator.apps.sandbox.x8i5.p1.openshiftapps.com/plugin-registry/v3/plugins/timonwong/shellcheck/latest/meta.yaml failed. Status code 404. Response body: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<html><head>

<title>404 Not Found</title>

</head><body>

<h1>Not Found</h1>

<p>The requested URL was not found on this server.</p>

</body></html>

Failed to run the workspace: "Plugins installation process failed. Error: Plugin brokering process for workspace workspacefv8x7o926av6vm7r failed with error: Failed to download plugin meta: failed to fetch plugin meta.yaml from URL 'https://codeready-codeready-workspaces-operator.apps.sandbox.x8i5.p1.openshiftapps.com/plugin-registry/v3/plugins/timonwong/shellcheck/latest/meta.yaml': Downloading https://codeready-codeready-workspaces-operator.apps.sandbox.x8i5.p1.openshiftapps.com/plugin-registry/v3/plugins/timonwong/shellcheck/latest/meta.yaml failed. Status code 404. Response body: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL was not found on this server.</p> </body></html> "

Issue Analytics

State:
Created 2 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

ibuziukcommented, Jul 15, 2021

@ericwill sounds good, so will let the plugins team to handle the fixup cc: @svor

1reaction

ericwillcommented, Jul 15, 2021

@ericwill could you please clarify if Eclipse Che supports multiple plugin registries?

I don’t believe so, and even if it was supported we cannot enable it in Dev Sandbox because you will have plugin collisions.

The fix to this issue is to add the registryUrl to the dogfooding devfile. We do this already for che-docs: https://github.com/eclipse/che-docs/blob/e3b942c33b37ff5b4c7c811fc5f49509aed57696/devfile.yaml#L29-L36

Top Results From Across the Web

The "shellcheck" plugin doesn't work #19376 - GitHub

Set prefernces "shellcheck.executablePath: /bin/shellcheck" · Go inside created workspace and open the "test.sh" file · Verify shellcheck features ...

Chapter 4. Known issues Red Hat OpenShift Dev Spaces 3.0

A workspace using Java with the JBoss EAP 7.3 devfile fails with the following error message: No delegateCommandHandler for vscode.java.startDebugSession .

ShellCheck - Visual Studio Marketplace

Integrates ShellCheck into VS Code, a linter for Shell scripts. Latest version VS Marketplace installs VS Marketplace downloads Open VSX downloads. Quick start....

eclipse/che 7.30.0 on GitHub - NewReleases.io

[Solved] Workspace fails to pull redhat image. "no available registry endpoint: could not resolve digest for" Any ideas? #19582; Add the "OWNERS" file...