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

Use `dsc` to update DevSpaces from `latest` to `next` build

XMLWordPrintable

    • False
    • None
    • False

      As of CRW-3877, we can deploy DS 3.latest or 3.next to an OCP cluster.

      But what doesn't is that we can't use dsc to then do an update from 3.4 / latest -> 3.5 / next, to test upgrade paths between releases:

      $➔ /tmp/dsc-350/dsc/bin/dsc server:deploy --olm-channel=next
› Current Kubernetes context: 'openshift-operators/api-ci-ln-ng4x4gb-72292-origin-ci-int-gce-dev-rhcloud-com:6443/kube:admin'
  ✔ Verify Kubernetes API...[1.24]
  ✔ OpenShift version: [4.11]
 ›   Warning: Red Hat OpenShift Dev Spaces has been already deployed. Use server:start command to start a stopped Red Hat OpenShift Dev Spaces instance.

$➔ /tmp/dsc-350/dsc/bin/dsc server:update 
› Current Kubernetes context: 'openshift-operators/api-ci-ln-ng4x4gb-72292-origin-ci-int-gce-dev-rhcloud-com:6443/kube:admin'
  ✔ Verify Kubernetes API...[1.24]
  ❯ Red Hat OpenShift Dev Spaces operator pre-update check
    ✖ Check InstallPlan approval strategy...[Automatic]
      → Use 'dsc server:update' command only with Manual InstallPlan approval strategy.
    Error: Command server:update failed with the error: Use 'dsc server:update' command only with Manual InstallPlan approval strategy. See details: /home/nboldt/.cache/dsc/error.log.

      How hard would it be to add the ability to deploy a new catalog source from another IIB, then trigger the update process?

      Current workaround could be to run

      ./installCatalogSourceFromIIB.sh --install-operator devspaces --channel fast --quay --iib quay.io/devspaces/iib:next-v4.11-x86_64

      and then watch the subscription update happen automatically from the new catalog source?

      I'm thinking one of these commands would be useful:

      • dsc server:deploy --olm-channel=next (even if 3.4 is already deployed, start over and deploy 3.5 on top to allow the upgrade to happen)
      • dsc server:update --olm-channel=next (apply just the new IIB/catalog source/subscription and let OLM handle the update from the `fast` channel)

      This should also work for installing 3.4 from RHEC `stable` channel, and being able to update to quay `fast` channel, for either `latest` or `next` tags.

        1. screenshot-4.png
          screenshot-4.png
          13 kB
        2. screenshot-3.png
          screenshot-3.png
          123 kB
        3. screenshot-2.png
          screenshot-2.png
          14 kB
        4. screenshot-1.png
          screenshot-1.png
          284 kB

              abazko Anatolii Bazko
              abazko Anatolii Bazko
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: