Cannot create workspace from Custom devfile when using namespace placeholder like <workspaceid>-che

[guydog28]

Describe the bug

It seems, when using placeholders to create workspaces in new namespaces, that the system attempts to validate the namespace name literally, without replacing the placeholder text. So a namespace like <workspaceid>-che will not even attempt to be created. Creating a workspace with the exact same devfile into the same namespace works if the devfile is added to the devfile registry and is create by clicking the item in the Getting Started pane.

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

Expected behavior

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2-0-g52c56ce", GitCommit:"b66f2d3", GitTreeState:"clean", BuildDate:"2020-08-11T15:26:36Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-15T16:51:04Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Screenshots

Installation method

• chectl
  • using operator installer
  • provide an output of chectl version: chectl/7.17.0 darwin-x64 node-v10.22.0
• OperatorHub
• I don't know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: please specify

Eclipse Che Logs

Additional context

This can be worked around by adding the devfile to the devfile registry, and clicking it from getting started, which seems to bypass this erroneous check and create the generated namespace. However the workspace will not start still, due to #17631

[guydog28]

Any updates here? It looks like 17631 was resolved for 7.19.0, but this one causes just as much harm, as it is not possible to create a workspace from a devfile, you can only click a Stack from Getting Started.

[guydog28]

As of 7.21.0, this is still an issue. Any updates? It appears to have changed now, that it now generates a proper workspace name, but the error is that custom namespaces are not allowed (which is by design) but this is not technically a custom namespace - it is generated as expected.

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