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

vscode-openshift-connector container going into CrashLoopBackOff state at the time of creating workspace on power for NodeConfigMap workspace

XMLWordPrintable

    • False
    • False
    • Undefined
    • Hide
      • create NodeConfigMap workspace (manually or automation)
      • go to <user>-codeready namespace, check pods. that is going in to CrashLoopBackOff state
      • state change history is: Running
        OOMKilled
        CrashLoopBackOff
        Running
      Show
      create NodeConfigMap workspace (manually or automation) go to <user>-codeready namespace, check pods. that is going in to CrashLoopBackOff state state change history is: Running OOMKilled CrashLoopBackOff Running

      workaround is to modify memory limit of below to "2.5GB" in devfile

      id: redhat/vscode-openshift-connector/latest
type: chePlugin
alias: openshift-connector
memoryLimit: 2.5Gi

        1. image-2021-03-03-18-46-02-894.png
          49 kB
          dipiki joahi
        2. image-2021-03-04-17-21-59-175.png
          22 kB
          dipiki joahi

              ericwill@redhat.com Eric Williams
              djoahi dipiki joahi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: