chectl server:deploy --skip-devworkspace-operator is not working

[dkwon17]

Describe the bug

With chectl (next), I ran the following command to install Eclipse Che on my OpenShift cluster:

chectl server:deploy \
    -p openshift \
    --batch \
    --telemetry=off \
    --skip-devworkspace-operator \
    --chenamespace=eclipse-che \
    --k8spodwaittimeout=86400 \
    --k8spodreadytimeout=86400

despite the --skip-devworkspace-operator field, I noticed that DWO was installed:

Che version

next (development version)

Steps to reproduce

Run

chectl server:deploy \
    -p openshift \
    --batch \
    --telemetry=off \
    --skip-devworkspace-operator \
    --chenamespace=eclipse-che \
    --k8spodwaittimeout=86400 \
    --k8spodreadytimeout=86400

on an OpenShift cluster.

Expected behavior

The DWO CSV should not be created.

Runtime

OpenShift

Screenshots

I noticed this issue in the DWO happy path test failure: devfile/devworkspace-operator#1685

What happened was:

• DWO is installed onto the cluster with make install
• chectl server:deploy -skip-devworkspace-operator is used to install che without DWO
• However, chectl server:deploy -skip-devworkspace-operator creates another DWO instance onto the cluster, causing the happy path test failure

Installation method

chectl/next

Environment

macOS

Eclipse Che Logs

Additional context

No response

[tolusha]

Hello @dkwon17,

The --skip-devworkspace-operator flag behaves a bit differently on OpenShift.

If the flag is not provided, chectl deploys either the next or stable version, depending on whether the chectl build itself is the next or stable release.

When the flag is omitted, the DevWorkspace Operator (DWO) is installed automatically by OLM because it is a dependency of the Che Operator.

[dkwon17]

For OpenShift, the DWO is installed automatically with the flag is not omitted, is that expected?

[dkwon17]

Closing, expected behaviour if DWO subscription object does not exist. If it does not exist, chectl will still attempt to install DWO.