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

CRW 2.8.0 workspace startup failure message is misleading when mkdir pod reached timeout

    XMLWordPrintable

Details

    • False
    • False
    • Hide
      = Misleading error message for a workspace failure caused by the `mkdir` Pod timeout

      A lack of {ocp} cluster resources causes a failure. This failure causes a misleading message: *Your session has expired. Please, log in to {prod-short} again to get access to your OpenShift account.*

      .Workaround

      * Provide more resources to the {ocp} cluster.
      Show
      = Misleading error message for a workspace failure caused by the `mkdir` Pod timeout A lack of {ocp} cluster resources causes a failure. This failure causes a misleading message: *Your session has expired. Please, log in to {prod-short} again to get access to your OpenShift account.* .Workaround * Provide more resources to the {ocp} cluster.
    • Workaround Exists
    • Hide

      Add more resources (nodes) to OCP instance.

      Refresh or re-login would not help.

      Show
      Add more resources (nodes) to OCP instance. Refresh or re-login would not help.

    Description

      Test scenario: 
      1. Deploy CRW 2.8.0.RC-04-26 to QE OCP 4.7 on AWS from Operator Hub with lack of resource
      2. Open Dashboard and log into it as OS Auth user
      3. Try to start Java Maven workspace

      Expected result: Dashboard Progress shows error message which crw server returns crw-server-logs.txt:

      Unable to perform '[mkdir, -m, 777, -p, /tmp/job_mount/workspace5frdg50h50khqq6w/che-logs-che-plugin-broker/]' command for the workspace 'workspace5frdg50h50khqq6w' cause: 'Waiting for pod 'mkdir-workspace5frdg50h50khqq6w' reached timeout'

       
      Actually result: Dashboard Progress has shown misleading message with html code instead of link inside:

      Your session has expired. Please login to Che again to get access to your OpenShift account

       

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. CRW-1920 CRW 2.9.0 workspace failed to start because was unable to attach or mount volumes for default token

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

          Bug - A problem that impairs or prevents the functions of the product. CRW-2018 Your session has expired. Please login to Che again to get access to your OpenShift account

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              skabashn Sergii Kabashniuk
              dnochevn Dmytro Nochevnov
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: