-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.19
-
Quality / Stability / Reliability
-
False
-
-
1
-
Critical
-
No
-
None
-
Rejected
-
NI&D Sprint 269, NI&D Sprint 270
-
2
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
Found failing test in CI:
: [sig-arch] Managed cluster should set requests but not limits [Suite:openshift/conformance/parallel]
{ fail [github.com/openshift/origin/test/extended/operators/resources.go:223]: Pods in platform namespaces are not following resource request/limit rules or do not have an exception granted:
apps/v1/Deployment/openshift-operators/servicemesh-operator3/container/sail-operator defines a limit on cpu of 500m which is not allowed (rule: "apps/v1/Deployment/openshift-operators/servicemesh-operator3/container/sail-operator/limit[cpu]")
apps/v1/Deployment/openshift-operators/servicemesh-operator3/container/sail-operator defines a limit on memory of 512Mi which is not allowed (rule: "apps/v1/Deployment/openshift-operators/servicemesh-operator3/container/sail-operator/limit[memory]")
Ginkgo exit error 1: exit with code 1}
Version-Release number of selected component (if applicable):
4.19.0-0.nightly-2025-04-04-170728
How reproducible:
100%
Steps to Reproduce:
1. Trigger Origin CI test with GatewayAPIController featuregate 2.
3.
Actual results:
Failing test
Expected results:
CI Passed
Additional info:
https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29644/pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-techpreview/1908704168583892992
- is related to
-
-
- New
-
- links to
-
RHEA-2024:11038
OpenShift Container Platform 4.19.z bug fix update