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

[KI] CVE update for 3.5.0 may break upgrade path

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Hide
      = Upgrading {prod-short} from 3.5 to 3.6 might require manual steps

      There is a known issue when updating to version 3.6: clusters that were updated to `devspacesoperator.v3.5.0-0.1682130576.p` require additional steps from administrators as a workaround.

      .Workaround

      . Go to the OpenShift web console.

      . Delete your existing *{prod}* Operator subscription and the `devspaces` CSV.
      +
      NOTE: This does not remove any of the deployed pods or running workspaces.

      . Install the latest *{prod}* Operator subscription.

      . Wait until all pods are replaced by new ones before opening the dashboard or loading workspaces.

      Alternatively, you can link:https://issues.redhat.com/browse/CRW-4355?focusedId=22287747&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-22287747[use the `oc` command-line tool].
      Show
      = Upgrading {prod-short} from 3.5 to 3.6 might require manual steps There is a known issue when updating to version 3.6: clusters that were updated to `devspacesoperator.v3.5.0-0.1682130576.p` require additional steps from administrators as a workaround. .Workaround . Go to the OpenShift web console. . Delete your existing *{prod}* Operator subscription and the `devspaces` CSV. + NOTE: This does not remove any of the deployed pods or running workspaces. . Install the latest *{prod}* Operator subscription. . Wait until all pods are replaced by new ones before opening the dashboard or loading workspaces. Alternatively, you can link: https://issues.redhat.com/browse/CRW-4355?focusedId=22287747&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-22287747 [use the `oc` command-line tool].
    • Known Issue
    • Done

      Issue is simply for documenting a KI caused by

      • CWFHEALTH-2003
      • CLOUDWF-9099
      • CLOUDDST-18632

      Story goes like this:

      1. We released 3.5.0.

      2. Then Freshmaker did its usual update process for 3.5-142.1679521113

      3. Then it released a broken update that omitted the `olm.substitutesFor` annotation (CWFHEALTH-2003), and pruned the 3.5.0 release from the catalog (CLOUDWF-9099, CLOUDDST-18632).

      So currently, there are TWO possible "heads" of the 3.5.z stream:

      • devspacesoperator.v3.5.0-0.1682130576.p, and
      • devspacesoperator.v3.5.0

      The borked v3.5.0-0.1682130576.p is being removed in CLOUDDST-18632, and the original 3.5.0 is being put back.

      But because of the possibility of having a broken upgrade path from 3.5.* to 3.6.0, there's a simple workaround.

      If you have installed v3.5.0-0.1682130576.p (from container image devspaces-bundle-image:3.5-142.1682130577 then you will need to:

      • wait for 3.6.0 to be available in RHEC
      • delete your existing subscription to the 3.5 operator
      • install a new operator subscription for 3.6.0
      • wait as pods are updated from 3.5 to 3.6, like in a normal automated subscription update

      NOTE:

      The CVE fix in 3.5-142.1682130577 is also in 3.6.0

        1. Screenshot from 2023-05-17 19-53-39.png
          Screenshot from 2023-05-17 19-53-39.png
          36 kB
        2. ds_3.5.0_3.6.0.png
          ds_3.5.0_3.6.0.png
          120 kB

              rhn-support-mleonov Max Leonov
              nickboldt Nick Boldt
              Dmytro Nochevnov Dmytro Nochevnov
              Max Leonov Max Leonov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: