devfiles v1 is not working with devWorkspace.enabled
See original GitHub issueDescribe the bug
Starting workspace in eclipse che nightly is not working on openshift 4.7 and openshft 4.8.
Che Server Error:
2021-07-02 18:47:23,838[aceSharedPool-0] [WARN ] [.i.k.KubernetesInternalRuntime 257] - Failed to start Kubernetes runtime of workspace workspacep0tltzdq3p86epc8.
org.eclipse.che.workspace.infrastructure.kubernetes.KubernetesInfrastructureException: Failure executing: POST at: https://172.30.0.1/apis/route.openshift.io/v1/namespaces/flacatus-che/routes. Message: Route.route.openshift.io "routel05isyes" is invalid: spec.host: Invalid value: "routeerybyw.": host must conform to DNS 952 subdomain conventions. Received status: Status(apiVersion=v1, code=422, details=StatusDetails(causes=[StatusCause(field=spec.host, message=Invalid value: "routeerybyw.": host must conform to DNS 952 subdomain conventions, reason=FieldValueInvalid, additionalProperties={})], group=route.openshift.io, kind=Route, name=routel05isyes, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=Route.route.openshift.io "routel05isyes" is invalid: spec.host: Invalid value: "routeerybyw.": host must conform to DNS 952 subdomain conventions, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Inval...
at org.eclipse.che.workspace.infrastructure.openshift.project.OpenShiftRoutes.create(OpenShiftRoutes.java:53)
at org.eclipse.che.workspace.infrastructure.openshift.OpenShiftInternalRuntime.createRoutes(OpenShiftInternalRuntime.java:166)
at org.eclipse.che.workspace.infrastructure.openshift.OpenShiftInternalRuntime.startMachines(OpenShiftInternalRuntime.java:128)
at org.eclipse.che.workspace.infrastructure.kubernetes.KubernetesInternalRuntime.internalStart(KubernetesInternalRuntime.java:214)
at org.eclipse.che.api.workspace.server.spi.InternalRuntime.start(InternalRuntime.java:141)
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes$StartRuntimeTask.run(WorkspaceRuntimes.java:964)
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:38)
at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(Unknown Source)
at io.micrometer.core.instrument.internal.TimedRunnable.run(TimedRunnable.java:44)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.eclipse.che.commons.observability.CountedThreadFactory.lambda$newThread$0(CountedThreadFactory.java:75)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://172.30.0.1/apis/route.openshift.io/v1/namespaces/flacatus-che/routes. Message: Route.route.openshift.io "routel05isyes" is invalid: spec.host: Invalid value: "routeerybyw.": host must conform to DNS 952 subdomain conventions. Received status: Status(apiVersion=v1, code=422, details=StatusDetails(causes=[StatusCause(field=spec.host, message=Invalid value: "routeerybyw.": host must conform to DNS 952 subdomain conventions, reason=FieldValueInvalid, additionalProperties={})], group=route.openshift.io, kind=Route, name=routel05isyes, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=Route.route.openshift.io "routel05isyes" is invalid: spec.host: Invalid value: "routeerybyw.": host must conform to DNS 952 subdomain conventions, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Invalid, status=Failure, ...
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:639)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:578)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:543)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:504)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleCreate(OperationSupport.java:292)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:893)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.create(BaseOperation.java:372)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.create(BaseOperation.java:86)
at org.eclipse.che.workspace.infrastructure.openshift.project.OpenShiftRoutes.create(OpenShiftRoutes.java:51)
... 12 common frames omitted
Workspace used to start: “https://raw.githubusercontent.com/eclipse-che/che-devfile-registry/master/devfiles/go/devfile.yaml”
Che version
- latest
- nightly
- other: please specify
Steps to reproduce
Deploy che using chectl server:deploy --platform=openshift --installer=olm
Expected behavior
Runtime
- kubernetes (include output of
kubectl version
) - Openshift (include output of
oc version
) - minikube (include output of
minikube version
andkubectl version
) - minishift (include output of
minishift version
andoc version
) - docker-desktop + K8S (include output of
docker version
andkubectl version
) - other: (please specify)
Screenshots
Installation method
- chectl
- provide a full command that was used to deploy Eclipse Che (including the output)
- provide an output of
chectl version
command
- OperatorHub
- I don’t know
Environment
- my computer
- Windows
- Linux
- macOS
- Cloud
- Amazon
- Azure
- GCE
- other (please specify)
- Dev Sandbox (workspaces.openshift.com)
- other: please specify
Eclipse Che Logs
Additional context
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Devfile v2 and the DevWorkspace Operator - Part 1
Although most of the work has been completed, Che with the DevWorkspace enabled is not ready for production yet. Here is a list...
Read more >Chapter 4. Known issues Red Hat OpenShift Dev Spaces 3.0
On IBM Z and IBM Power, the debugging features cannot be activated in the Go workspace in OpenShift Dev Spaces 3.0. Delve, the...
Read more >Introduction to Devfile - GitHub Pages
A list of projects: the source code repositories; A list of commands: actions to manage the workspace components like running the dev tools,...
Read more >Re: [che-dev] How workspace routing works in devworkspace ...
We may use devfile v1 vs devfile v2 to > distinguish the 2 engines in the ... an issue since we do control...
Read more >Devfile v2 and IDE plug-ins in Eclipse Che - Medium
You can still work with your previous workspaces and devfile v1. ... To enable devWorkspace, it uses a custom spec object for Che...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
v1 devfiles are expected to work with the devworkspace enabled I believe. There has been an issue reported some time ago, but not sure if it is relevant for the current context - https://github.com/eclipse/che/issues/20052
expected behavior