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

[proxy] Dev workspace V2 devfiles have empty workspace panel

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Hide
      = *Workspace* panel in Che-Theia workspaces might appear blank

      In workspaces that use the default Che-Theia IDE in a proxied environment, the *Workspace* panel might appear blank rather than showing available commands, terminals, and applications.

      .Workaround

      . Run `$ oc edit proxy cluster`.
      . Add `172.30.0.1` to the `spec.noProxy` property.
      . Run the `oc` command in the project where *devworkspace-controller-manager* is deployed, `openshift-operators` or `openshift-devspaces`:
      +
      [source,terminal]
      ----
      `$ oc rollout restart -n __<project>__ deploy/devworkspace-controller-manager`
      ----
      Show
      = *Workspace* panel in Che-Theia workspaces might appear blank In workspaces that use the default Che-Theia IDE in a proxied environment, the *Workspace* panel might appear blank rather than showing available commands, terminals, and applications. .Workaround . Run `$ oc edit proxy cluster`. . Add `172.30.0.1` to the `spec.noProxy` property. . Run the `oc` command in the project where *devworkspace-controller-manager* is deployed, `openshift-operators` or `openshift-devspaces`: + [source,terminal] ---- `$ oc rollout restart -n __<project>__ deploy/devworkspace-controller-manager` ----
    • Documented as Known Issue
    • Workaround Exists
    • Hide

      1. Run `$ oc edit proxy cluster`.
      2. Add `172.30.0.1` to the `spec.noProxy` property.
      3. Run `$ oc rollout restart -n openshift-operators deploy/devworkspace-controller-manager`

      Show
      1. Run `$ oc edit proxy cluster`. 2. Add `172.30.0.1` to the `spec.noProxy` property. 3. Run `$ oc rollout restart -n openshift-operators deploy/devworkspace-controller-manager`
    • Hide
      1. Set up proxied cluster.
      2. Install Dev Spaces 3.0 (or CRW 2.15.10z with DWO = enabled)
      3. Create che cluster
      4. Open dashboard
      5. Create new workspace 

      In the workspace UI,  right side panel workspaces with box icon is empty

      Show
      Set up proxied cluster. Install Dev Spaces 3.0 (or CRW 2.15.10z with DWO = enabled) Create che cluster Open dashboard Create new workspace  In the workspace UI,  right side panel workspaces with box icon is empty

    Description

      When workspace is started from a DevWorkspace V2 devfile, UI does not show options like build, run in right side panel workspaces

      Attachments

        1. browserlogs.io-16
          53 kB
          Yogita Kulkarni
        2. CRW_2_15_102_ouput_log.txt
          23 kB
          Yogita Kulkarni
        3. ds-3-1-0_dwo-0-15-2.png
          395 kB
          Dmytro Nochevnov
        4. eclipse-che-7.45.png
          269 kB
          Dmytro Nochevnov
        5. empty_workspaces.png
          241 kB
          Yogita Kulkarni
        6. empty-workspace-view-in-airgap-x86-2022-05-13 15-47-03.png
          155 kB
          Dmytro Nochevnov
        7. go_theia_container_log.log
          136 kB
          Nick Boldt
        8. golang_build.PNG
          60 kB
          Yogita Kulkarni
        9. image-2022-05-10-14-21-20-369.png
          220 kB
          Yogita Kulkarni
        10. image-2022-05-13-17-28-45-348.png
          297 kB
          Yogita Kulkarni
        11. image-2022-05-31-10-01-37-718.png
          289 kB
          Yogita Kulkarni
        12. theia-ide-logs.log
          122 kB
          Yogita Kulkarni

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. CRW-3032 [airgap] "tunneling socket could not be established, statusCode=403" error when run task

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-3050 [proxy, airgap] Start of DS 3.0.0.RC-06-03 workspaces was stuck on "Waiting for workspace to start" step on airgap OCP 4.10

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          links to

          GitHub eclipse-che/che-operator#1387: fix: Add `KUBERNETES_SERVICE_HOST` to non proxy list

          Activity

            People

              ibuziuk@redhat.com Ilya Buziuk
              yogitakulkarni Yogita Kulkarni (Inactive)
              Max Leonov Max Leonov
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: