Loading...

XML

Word

Printable

Blocked:
False
Ready:
False
Release Note Text:
Undefined
Steps to Reproduce:
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
Market:

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

is related to

CRW-1637 Add resource limits/requests to the devfiles and plugins in the registries

CRW-1635 vscode-python container going into CrashLoopBackOff state at the time of creating workspace on power for Python workspace

relates to

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