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

Details

    • 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

    Description

      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

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users CRW-1637 Add resource limits/requests to the devfiles and plugins in the registries

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-1635 vscode-python container going into CrashLoopBackOff state at the time of creating workspace on power for Python workspace

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

          Bug - A problem that impairs or prevents the functions of the product. CRW-1633 vscode-camelk container going into CrashLoopBackOff state at the time of creating workspace on power for ApacheCamelK workspace

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: