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

vscode-camelk container going into CrashLoopBackOff state at the time of creating workspace on power for ApacheCamelK workspace

    XMLWordPrintable

Details

    • False
    • False
    • Undefined
    • Hide
      • create ApacheCamelK 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 ApacheCamelK 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

    Description

      workaround is to modify memory limit of "vscode-camelk" to "1.5GB" in devfile

      image: "registry.redhat.io/codeready-workspaces/plugin-kubernetes-rhel8:2.8"
name: vscode-camelk
memoryLimit: "1.5G"

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. CRW-1634 vscode-openshift-connector container going into CrashLoopBackOff state at the time of creating workspace on power for NodeConfigMap workspace

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

          Activity

            People

              djoahi dipiki joahi (Inactive)
              djoahi dipiki joahi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: