che Timeout error During Eclipse Che Installation on CRC Cluster (M4 MacBook)

Describe the bug

I was trying to install Che following Eclipse Che Documentation on my M4 macbook on CRC cluster. However, when I was trying to install it, I was getting timeout errors during Create Subscription devworkspace-operator step

I tried this command multiple times, but I was repeatedly getting same error:

chectl server:deploy --platform crc

Error: Command server:deploy failed with the error: Cannot create property 'context' on string 'Timeout reached while waiting for "devworkspace-operator" subscription is ready.'

Even if I specify timeout using the flags, I don't see any effect:

chectl server:deploy --platform crc --k8spoddownloadimagetimeout=60m --k8spodwaittimeout=60m --k8spodreadytimeout=60m --k8spoderrorrechecktimeout=60m


Error: Command server:deploy failed with the error: Cannot create property 'context' on string 'Timeout reached while waiting for "devworkspace-operator" subscription is ready.'

It might be possible that I'm doing it incorrectly or have missed something.

However, when I tried the same steps on my Linux machine, I was able to install Eclipse Che. I would appreciate if I could get some guidance regarding this.

CRC Cluster Details :

CRC version: 2.49.0+e843be
OpenShift version: 4.18.2
MicroShift version: 4.18.2

Che version

7.101@latest

Steps to reproduce

Download chectl/7.101.0 darwin-arm64 node-v18.18.0
Ensure CRC is running
Run chectl server:deploy --platform , command is failing on my m4 macos machine with timeout error

Expected behavior

Che should deploy successfully on a CRC cluster following the documented procedure, regardless of the operating system.

Runtime

CodeReady Container

Screenshots

No response

Installation method

chectl/latest

Environment

macOS

Eclipse Che Logs

› Current Kubernetes context: 'default/api-crc-testing:6443/kubeadmin'
  ✔ Verify Kubernetes API...[1.31]
  ✔ OpenShift version...[4.18]
  ✔ OpenShift Local preflight checklist
    ✔ Verify if oc is installed...[OK]
    ✔ Verify if OpenShift Local is installed...[OK]
    ✔ Verify if OpenShift Local is running...[OK]
    ✔ Retrieving OpenShift Local IP and domain for routes URLs...[127.0.0.1.nip.io]
  ✔ Create Namespace eclipse-che...[Exists]
  ✔ Start following Eclipse Che installation logs...[OK]
  ❯ Deploy Eclipse Che
    ❯ Install Dev Workspace operator
      ✔ Create CatalogSource devworkspace-operator...[Exists]
      ✖ Create Subscription devworkspace-operator
        Wait for Dev Workspace operator ready
      Create Subscription eclipse-che
      Eclipse Che Operator pod bootstrap
      Fetch CheCluster sample from a CSV
      Create CheCluster Custom Resource
Error: Command server:deploy failed with the error: Cannot create property 'context' on string 'Timeout reached while waiting for "devworkspace-operator" subscription is ready.' See details: /Users/rokumar/Library/Caches/chectl/error.log. Eclipse Che logs: /var/folders/w5/hm1ypjpd0811dtmnrrvqbj0m0000gn/T/chectl-logs/1745226646785.
    at newError (/usr/local/lib/chectl/lib/utils/utls.js:39:19)
    at wrapCommandError (/usr/local/lib/chectl/lib/utils/command-utils.js:54:32)
    at Deploy.<anonymous> (/usr/local/lib/chectl/lib/commands/server/deploy.js:82:65)
    at Generator.throw (<anonymous>)
    at rejected (/usr/local/lib/chectl/node_modules/tslib/tslib.js:167:69)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Cause: TypeError: Cannot create property 'context' on string 'Timeout reached while waiting for "devworkspace-operator" subscription is ready.'
    at /usr/local/lib/chectl/node_modules/listr/index.js:112:19
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Additional context

No response

Apr 21 '25 14:04 rohanKanojia

@tolusha please take a look

Apr 21 '25 15:04 RomanNikitenko

Try to rerun the deploy command just after the previous try failed: chectl server:deploy --platform crc
Inspect operator subscription: oc get subs devworkspace-operator -n openshift-operators -o yaml
Inspect catalog source: oc get catalogsources devworkspace-operator openshift-marketplace -o yaml

Apr 23 '25 08:04 tolusha

Thanks for your reply, I've followed your instructions. I'm sharing YAML output of these resources below:

Inspect operator subscription: oc get subs devworkspace-operator -n openshift-operators -o yaml

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  creationTimestamp: "2025-04-21T04:16:59Z"
  generation: 1
  labels:
    app.kubernetes.io/part-of: che.eclipse.org
    operators.coreos.com/devworkspace-operator.openshift-operators: ""
  name: devworkspace-operator
  namespace: openshift-operators
  resourceVersion: "114006"
  uid: afa7b69e-66d1-4e52-8ae1-7fdf41a70280
spec:
  channel: fast
  installPlanApproval: Automatic
  name: devworkspace-operator
  source: devworkspace-operator
  sourceNamespace: openshift-marketplace
status:
  catalogHealth:
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: certified-operators
      namespace: openshift-marketplace
      resourceVersion: "37224"
      uid: b0222790-6d20-4a0f-afc2-49e923d46de5
    healthy: true
    lastUpdated: "2025-04-21T04:17:11Z"
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: community-operators
      namespace: openshift-marketplace
      resourceVersion: "37345"
      uid: 613c8178-b6b3-47ea-a67c-4102db5890a7
    healthy: true
    lastUpdated: "2025-04-21T04:17:11Z"
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: devworkspace-operator
      namespace: openshift-marketplace
      resourceVersion: "37711"
      uid: c47f0664-8da3-49a9-98a9-7927d39b579a
    healthy: true
    lastUpdated: "2025-04-21T04:17:11Z"
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: redhat-marketplace
      namespace: openshift-marketplace
      resourceVersion: "37348"
      uid: 85a7748e-31c0-4a10-80b0-e1c23a29e2e3
    healthy: true
    lastUpdated: "2025-04-21T04:17:11Z"
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: redhat-operators
      namespace: openshift-marketplace
      resourceVersion: "37360"
      uid: 33730ec2-b28d-400e-9624-54cdbb915a88
    healthy: true
    lastUpdated: "2025-04-21T04:17:11Z"
  conditions:
  - lastTransitionTime: "2025-04-21T04:17:15Z"
    message: all available catalogsources are healthy
    reason: AllCatalogSourcesHealthy
    status: "False"
    type: CatalogSourcesUnhealthy
  - message: 'error using catalogsource openshift-marketplace/devworkspace-operator:
      failed to list bundles: rpc error: code = Unavailable desc = connection error:
      desc = "transport: Error while dialing: dial tcp 10.217.5.94:50051: connect:
      connection refused"'
    reason: ErrorPreventedResolution
    status: "True"
    type: ResolutionFailed
  lastUpdated: "2025-04-23T08:20:21Z"

Inspect catalog source: oc get catalogsources devworkspace-operator openshift-marketplace -o yaml

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  creationTimestamp: "2025-04-21T04:16:59Z"
  generation: 1
  labels:
    app.kubernetes.io/part-of: che.eclipse.org
  name: devworkspace-operator
  namespace: openshift-marketplace
  resourceVersion: "114064"
  uid: c47f0664-8da3-49a9-98a9-7927d39b579a
spec:
  image: quay.io/devfile/devworkspace-operator-index:release
  sourceType: grpc
  updateStrategy:
    registryPoll:
      interval: 15m
status:
  connectionState:
    address: devworkspace-operator.openshift-marketplace.svc:50051
    lastConnect: "2025-04-23T08:20:31Z"
    lastObservedState: TRANSIENT_FAILURE
  latestImageRegistryPoll: "2025-04-21T04:34:15Z"
  registryService:
    createdAt: "2025-04-21T04:16:59Z"
    port: "50051"
    protocol: grpc
    serviceName: devworkspace-operator
    serviceNamespace: openshift-marketplace

Apr 23 '25 08:04 rohanKanojia

@dkwon17 Basically quay.io/devfile/devworkspace-operator-index:release is built for amd64 platform only. Unfortunately it is not possible to deploy a DWO from a stable channel.

@rohanKanojia Try chectl server:deploy --platform crc --olm-channel next but eventually we bumped into https://github.com/eclipse-che/che/issues/23128#issuecomment-2750598428 Currently, it is possible to deploy Eclipse Che on Minikube or any other Kubernetes provider running on the ARM64 platform but not CRC/OpenShift :(

Apr 28 '25 15:04 tolusha

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.

Nov 13 '25 08:11 che-bot