Procedure

1. Verify that the OpenShift Dev Spaces Operator CSV shows the expected version and Succeeded phase:

   $ oc get csv -n openshift-devspaces -o custom-columns='NAME:.metadata.name,PHASE:.status.phase,VERSION:.spec.version'

   Copy code to clipboard

   Expected output:

   NAME                        PHASE       VERSION
   devspacesoperator.v3.29.0   Succeeded   3.29.0

   Copy code to clipboard

2. Verify that the CheCluster custom resource reports Active phase and the correct version:

   $ oc get checluster devspaces -n openshift-devspaces -o jsonpath='Phase: {.status.chePhase}, Version: {.status.cheVersion}'

   Copy code to clipboard

   Expected output:

   Phase: Active, Version: 3.29.0

   Copy code to clipboard

3. Verify that all OpenShift Dev Spaces pods in the openshift-devspaces namespace are running and ready:

   $ oc get pods -n openshift-devspaces

   Copy code to clipboard

   All pods should show Running status with all containers ready.

4. Verify that the OpenShift Dev Spaces dashboard is accessible:

   $ oc get checluster devspaces -n openshift-devspaces -o jsonpath='{.status.cheURL}'

   Copy code to clipboard

   Open the returned URL in a browser and confirm the login page loads.

5. Verify that the Dev Workspace Operator is running the expected version:

   $ oc get csv -n openshift-operators -o custom-columns='NAME:.metadata.name,PHASE:.status.phase' | grep devworkspace

   Copy code to clipboard

   The Dev Workspace Operator CSV should show Succeeded phase.

6. Start a test workspace from the OpenShift Dev Spaces dashboard to confirm that workspaces function correctly after the upgrade.

Procedure

1. Delete the devworkspace-controller namespace that contains the failing pod.

2. Update DevWorkspace and DevWorkspaceTemplate Custom Resource Definitions (CRD) by setting the conversion strategy to None and removing the entire webhook section:

   spec:
     ...
     conversion:
       strategy: None
   status:
   ...

   Copy code to clipboard
   Tip

   You can find and edit the DevWorkspace and DevWorkspaceTemplate CRDs in the Administrator perspective of the OpenShift web console by searching for DevWorkspace in Administration → CustomResourceDefinitions.

   Note

   The DevWorkspaceOperatorConfig and DevWorkspaceRouting CRDs have the conversion strategy set to None by default.

3. Remove the Dev Workspace Operator subscription:

   $ oc delete sub devworkspace-operator \
   -n <devworkspace_operator_namespace>

   Copy code to clipboard

   where:

   <devworkspace_operator_namespace>

   The project where the Dev Workspace Operator is installed. For OpenShift Dev Spaces 3.29, this is typically openshift-devspaces. For standalone Dev Workspace Operator installations, this is openshift-operators.

4. Get the Dev Workspace Operator CSVs in the <devworkspace_operator.vX.Y.Z> format:

   $ oc get csv | grep devworkspace

   Copy code to clipboard

5. Remove each Dev Workspace Operator CSV:

   $ oc delete csv <devworkspace_operator.vX.Y.Z> \
   -n <devworkspace_operator_namespace>

   Copy code to clipboard

6. Re-create the Dev Workspace Operator subscription:

   $ cat <<EOF | oc apply -f -
   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
     name: devworkspace-operator
     namespace: openshift-operators
   spec:
     channel: fast
     name: devworkspace-operator
     source: redhat-operators
     sourceNamespace: openshift-marketplace
     installPlanApproval: Automatic
     startingCSV: devworkspace-operator.v0.41.0
   EOF

   Copy code to clipboard

   installPlanApproval

   Automatic or Manual.

   Important

   For installPlanApproval: Manual, in the Administrator perspective of the OpenShift web console, go to Operators → Installed Operators and select the following for the Dev Workspace Operator: Upgrade available → Preview InstallPlan → Approve.