Loading...

XML

Word

Printable

Blocked:
False
Ready:
False
Release Note Text:

Hide
= Attempts to clone a workspace from a *Quick Add* sample result in an error under the `single-host` strategy

When using the `single-host` strategy for workspace exposure, attempting to clone a workspace from a *Quick Add* sample results in an error. There is currently no workaround for this issue.

Show
= Attempts to clone a workspace from a *Quick Add* sample result in an error under the `single-host` strategy When using the `single-host` strategy for workspace exposure, attempting to clone a workspace from a *Quick Add* sample results in an error. There is currently no workaround for this issue.
Release Note Status:
Documented as Known Issue

As part of ~~CRW-1639~~ CRW dogfooding instance has been switched from the multi-host to single host setup:

`serverExposureStrategy: single-host`

However, currently, it is not possible to clone workspace from the Get-Started samples, which results in the error:

It seems that after the switch the devfile-registry is updated incorrectly and point to the wrong location of the projects:

e.g. https://codeready-codeready-workspaces-operator.apps.che-dev.x6e0.p1.openshiftapps.com/devfile-registry/devfiles/05_php-cake/devfile.yaml

zip source points to non-existing location is - https://devfile-registry-codeready-workspaces-operator.apps.che-dev.x6e0.p1.openshiftapps.com/resources/cakephp-ex-cakephp-ex-master.zip

It looks like devfile-registry still tries to use single-host routes for obtaining samples. In reality, it should use smth. like https://codeready-codeready-workspaces-operator.apps.che-dev.x6e0.p1.openshiftapps.com/devfile-registry/resources/cakephp-ex-cakephp-ex-master.zip

However,