Incorrect path - https://che-plugin-registry.openshift.io/v3/plugins/eclipse/che-theia/7.0.0/meta.yaml

[manishpython]

While deploying Nodejs app in workspace, but getting below error:

The requested URL /v3/plugins/eclipse/che-theia/7.0.0/meta.yaml was not found on this server.

Full Workspace Start Logs

Cleaning /plugins dir
Starting Init Plugin Broker
Failed to download plugin meta: failed to fetch plugin meta.yaml from URL 'https://che-plugin-registry.openshift.io/v3/plugins/eclipse/che-theia/7.0.0/meta.yaml': Downloading https://che-plugin-registry.openshift.io/v3/plugins/eclipse/che-theia/7.0.0/meta.yaml failed. Status code 404. Response body: 

Not Found

The requested URL /v3/plugins/eclipse/che-theia/7.0.0/meta.yaml was not found on this server.

Error: Failed to run the workspace: "Plugins installation process failed. Error: Plugin broking process for workspace workspacewm7o9ae2ceq9bnwg failed with error: Failed to download plugin meta: failed to fetch plugin meta.yaml from URL 'https://che-plugin-registry.openshift.io/v3/plugins/eclipse/che-theia/7.0.0/meta.yaml': Downloading https://che-plugin-registry.openshift.io/v3/plugins/eclipse/che-theia/7.0.0/meta.yaml failed. Status code 404. Response body: 

Not Found

The requested URL /v3/plugins/eclipse/che-theia/7.0.0/meta.yaml was not found on this server.

Observed that it should be as per below

Incorrect path - https://che-plugin-registry.openshift.io/v3/plugins/eclipse/che-theia/7.0.0/meta.yaml
Correct path - https://che-plugin-registry.openshift.io/v3/plugins/eclipse/che-theia/7.0.0-next/meta.yaml

Kindly fix it.

[sleshchenko]

cc @vparfonov @ibuziuk
Looks like Plugin Registry on OpenShift.io should be updated

[sleshchenko]

@manishpython How did you deploy your Che? chectl, helm, ...?

[amisevsk]

I'll open a PR to update the registry, but it's worth noting that eclipse-che/che-plugin-registry@191df1e#diff-81a58be1dc1db6f64c386b8e5b5b2057L4 is a breaking change -- any workspaces that explicitly reference eclipse/che-theia/7.0.0-next will no longer work

[manishpython]

I depoyed Che on Openshift 3.11 successfully, but when working on nodejs app in workspace then face that issue. Thanks MS

…

On Fri 16 Aug, 2019, 18:01 Sergii Leshchenko, ***@***.***> wrote: @manishpython <https://github.com/manishpython> How did you deploy your Che? chectl, helm, ...? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14261>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC6O623R46TFPRXBXPPKZ73QE2MYNANCNFSM4IMGZAYA> .

[amisevsk]

@manishpython As a workaround while we get this resolved, you can update the configmap che on your OpenShift cluster. Adding the keys:

CHE_WORKSPACE_PLUGIN__REGISTRY__URL: https://che-plugin-registry.prod-preview.openshift.io/
CHE_WORKSPACE_DEVFILE__REGISTRY__URL: https://che-devfile-registry.prod-preview.openshift.io/

should fix the issue.

[ibuziuk]

@manishpython have you deployed against minishift? Could you please provide the info about how exactly you deployed Che? AFAIK minishift is the only flavour of che that still uses openshift.io registries

[rhopp]

If we want to continue supporting minishift addon, I guess it should take care about deploying registries as well... We cannot ensure, that registries versions on production openshift.io deployments are inline with Che addon version.

[ibuziuk]

I would rather deprecate minishift addon and focus on #10998 (part of deprecate single-user mode #10996)

[manishpython]

@manishpython As a workaround while we get this resolved, you can update the configmap che on your OpenShift cluster. Adding the keys:

CHE_WORKSPACE_PLUGIN__REGISTRY__URL: https://che-plugin-registry.prod-preview.openshift.io/
CHE_WORKSPACE_DEVFILE__REGISTRY__URL: https://che-devfile-registry.prod-preview.openshift.io/

should fix the issue.

Thanks, It works now.

[manishpython]

@manishpython have you deployed against minishift? Could you please provide the info about how exactly you deployed Che? AFAIK minishift is the only flavour of che that still uses openshift.io registries

No minishift, only used openshift container platform 3.11.

[johnmcollier]

FWIW, I'm seeing this issue too with eclipse/che-theia:7.0.0 on OpenShift 3.11. I deployed Che with ./deploy-che.sh and no plugin/devfile registry was deployed by default, so the OpenShift.io plugin registry was used instead, where eclipse/che-theia:7.0.0 doesn't exist, so workspace creation failed.

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

[manishpython]

Closing