-
Bug
-
Resolution: Not a Bug
-
Critical
-
2.13.0.GA
-
False
-
False
-
Workaround Exists
-
-
Next CRW 2.12.1 workspaces failed to start after update to CRW 2.13.0.RC-11-17 on OCP 4.8 on AWS because pod creation timeout exceeded:
- Red Hat Fuse
- NodeJS Mongo
- NodeJS Configmap
Add eth0 [10.131.1.58/23] from openshift-sdn Pulling image "registry.redhat.io/codeready-workspaces/pluginbroker-metadata-rhel8@sha256:728a36a0a7d5ed2007414b7a4a45bf4d6103ed6021f3fc5da461a583ce995359" Successfully pulled image "registry.redhat.io/codeready-workspaces/pluginbroker-metadata-rhel8@sha256:728a36a0a7d5ed2007414b7a4a45bf4d6103ed6021f3fc5da461a583ce995359" in 1.71160535s Created container pluginbroker-metadata-rhel8-728a36a0a7 Started container pluginbroker-metadata-rhel8-728a36a0a7 Starting plugin metadata broker List of plugins and editors to install - redhat/java8/latest - Java Linting, Intellisense, formatting, refactoring, Maven/Gradle support and more... - redhat/vscode-apache-camel/latest - Provides completion and documentation features for Apache Camel URI elements in XML DSL. - redhat/dependency-analytics/latest - Insights about your application dependencies: Security, License compatibility and AI based guidance to choose appropriate dependencies for your application. - eclipse/che-theia/latest - Eclipse Theia, get the latest release each day. All plugin metadata has been successfully processed Failed to run the workspace: "Pod creation timeout exceeded. -id: workspace3l0yplvloyhondfm.maven -message: null"
Next workspaces had started correctly after an update https://main-jenkins-csb-crwqe.apps.ocp4.prod.psi.redhat.com/job/CodereadyWorkspaces/job/e2e/job/complex/job/crwctl-flow/job/update-crw-crwctl/170/consoleFull:
- 05_cpp
- 03_java11-maven-gradle
- 05_dotnet
- 05_php-di
- 00_java11-maven-microprofile-xp3
- 05_python
- 00_java11-maven-microprofile-bootable
- 04_nodejs-simple
- 03_java11-maven-vertx-http-booster
- 03_java8-maven-spring-boot-http-booster
- 03_java11-maven-lombok
- 05_php-cake
- 00_java8-maven-eap
- 05_go
- 03_java11-maven-quarkus
- 03_java11-maven-vertx
- 03_camelk
Removal of admin-codeready OCP namespace didn't help: new admin-codeready namespace has created with the same "admin-codeready-core-resource-limits":
kind: LimitRange apiVersion: v1 metadata: name: admin-codeready-core-resource-limits namespace: admin-codeready uid: bac8aa07-c3f5-4f3f-bc72-7e5c04844f02 resourceVersion: '662677' creationTimestamp: '2021-11-19T17:36:55Z' managedFields: - manager: openshift-apiserver operation: Update apiVersion: v1 time: '2021-11-19T17:36:55Z' fieldsType: FieldsV1 fieldsV1: 'f:spec': 'f:limits': {} spec: limits: - type: Container max: cpu: '4' memory: 6Gi default: cpu: 500m memory: 1536Mi defaultRequest: cpu: 50m memory: 256Mi - type: Pod max: cpu: '4' memory: 12Gi
Problem hasn't been reproduced on OCP 4.9 Single Node and on OCP 3.11 on PSI OpenStack: https://main-jenkins-csb-crwqe.apps.ocp4.prod.psi.redhat.com/job/CodereadyWorkspaces/job/e2e/job/complex/job/crwctl-flow/job/update-crw-crwctl/159/
- is duplicated by
-
CRW-2567 Start of CRW 2.14.0 java workspace failed because of maven pod cpu usage limits
- Closed