Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3173

Stabilize test workspace creation in automated test pipelines

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • 3.1.0.GA
    • 3.1.0.GA
    • testing
    • None
    • False
    • None
    • False

      Default start workspace timeout = 5 minutes is too small when run automated devfile tests agains DS deployed to OCP on PSI OSP where network lags are observed from time to time, e.g.:
      https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/Testing/job/e2e/job/basic/job/typescript-tests/1763/consoleFull

      Solution: increase start workspace timeout using config of devworkspace operator controller [1]:

      cat <<EOF | oc apply -f -
      apiVersion: controller.devfile.io/v1alpha1
      kind: DevWorkspaceOperatorConfig
      metadata:
        name: devworkspace-operator-config
        namespace: openshift-operators
      config:
        workspace:
          progressTimeout: "10m"
      EOF
      

      [1] https://github.com/devfile/devworkspace-operator/blob/main/apis/controller/v1alpha1/devworkspaceoperatorconfig_types.go#L109-L113

              dnochevn Dmytro Nochevnov
              dnochevn Dmytro Nochevnov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: