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

Error creating DevWorkspace deployment with JetBrains CLion and Rider Editors: Init Container editor-injector has state CrashLoopBackOff

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Release Notes
    • Hide
      = Workspaces with JetBrains CLion or Rider fail to start with default per-workspace PVC size

      When you create a workspace that uses the JetBrains CLion or JetBrains Rider IDE with the `per-workspace` storage strategy, the workspace can fail to start. The `editor-injector` `init container` enters a `CrashLoopBackOff` state due to a "No space left on device" error.

      This issue occurs because the default persistent volume claim (PVC) size of `5Gi` is insufficient. The CLion IDE requires approximately 8.5 GB of disk space.

      *Workaround*

      To resolve this issue, configure a `PVC` size of at least 8.5 GB for the workspace.
      Show
      = Workspaces with JetBrains CLion or Rider fail to start with default per-workspace PVC size When you create a workspace that uses the JetBrains CLion or JetBrains Rider IDE with the `per-workspace` storage strategy, the workspace can fail to start. The `editor-injector` `init container` enters a `CrashLoopBackOff` state due to a "No space left on device" error. This issue occurs because the default persistent volume claim (PVC) size of `5Gi` is insufficient. The CLion IDE requires approximately 8.5 GB of disk space. *Workaround* To resolve this issue, configure a `PVC` size of at least 8.5 GB for the workspace.
    • Known Issue
    • Done
    • Workaround Exists
    • Hide

      To resolve this issue, configure a `PVC` size of at least 8.5 GB for the workspace.

      Show
      To resolve this issue, configure a `PVC` size of at least 8.5 GB for the workspace.

      Description of problem:

      Workaround

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Install Dev Spaces 3.23.0-RC.26.08 with per-workspace PVC storage strategy
      1. Go to User Dashboard and create Empty workspace using JetBrains CLion (desktop)
      2. Go to User Dashboard and create Empty workspace using JetBrains Rider IDE

      Actual results:

      Workspace failed to start:

      Error creating DevWorkspace deployment: Init Container editor-injector has state CrashLoopBackOff 


       

      CLion IDE

      There was "No space left on device" error message in "editor-injector" container logs:

      Downloading IDE binaries...
      tar: bin/clang/linux/x64/bin/clang-tidy: Wrote only 7680 of 10240 bytes
      tar: bin/clang/linux/x64/bin/clazy-standalone: Cannot write: No space left on device
       

      Rider IDE

      There was "No space left on device" error message in "editor-injector" container logs: workspacede7748c958564e27-69495d8779-ht4ts-editor-injector.log

      Expected results:

      Workspace started successfully.

      Reproducibility (Always/Intermittent/Only Once):

      Alwasy

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

      There was default PVC storage size 5Gi, and per-workspace PVC strategy.

      Configuration of Lombok Sample pod: pod-workspacede7748c958564e27-69495d8779-ht4ts.yaml

      The error reproduced on different OCP 4.18 cluster with default PVC storage size 5Gi.

      Workspace started successfully using JetBrains CLion and Rider IDEs in Dev Spaces 3.23.0-RC.26.08 deployed to DevSandbox stage with increased PVC storage size.

      Error hasn't been reproduced with the different JetBrains Ultimate, JetBrains PhpStorm Editors on the same cluster with default PVC storage size 5Gi.

       *

              azatsary Artem Zatsarynnyi
              dnochevn Dmytro Nochevnov
              Gaurav Trivedi Gaurav Trivedi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: