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

Update CRW from multi host to single host broke "Create Workspace" page on Dashboard UI

XMLWordPrintable

    • False
    • False
    • Hide
      = Updating the {prod-short} instance from the multi-host to the single-host strategy breaks the Create Workspace UI

      After patching the {prod-short} {prod-ver} instance from `multi-host` to `single-host`, the Dashboard *Create Workspace* page displays an incomplete UI with missing icons.

      .Workaround

      * Re-deploy the devfile registry Pod after the update.
      Show
      = Updating the {prod-short} instance from the multi-host to the single-host strategy breaks the Create Workspace UI After patching the {prod-short} {prod-ver} instance from `multi-host` to `single-host`, the Dashboard *Create Workspace* page displays an incomplete UI with missing icons. .Workaround * Re-deploy the devfile registry Pod after the update.
    • Workaround Exists
    • Hide

      Re-deploy devfile registry pod after update.

      Show
      Re-deploy devfile registry pod after update.

      Test case:
      1. Install CRW 2.10.0 with default multi-host strategy.
      2. Patch Che Cluster YAML:
      change:
      "serverExposureStrategy: multi-host"
      to
      "serverExposureStrategy: single-host"
      3. Let operator finish update.
      4. Open Dashboard and go to "Create Workspace" page

      Actual result: broken icons of workspace tales, and an error message when try to create workspace:

      Root cause: devfile registry returns devfiles/index.json with links for multi-host strategy, instead of single-host one:
      index.json

      Note: CRW 2.10.0.RC Single Host installation works as expected.

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

                Created:
                Updated:
                Resolved: