-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
None
-
False
-
-
0
-
None
-
None
-
None
-
uShift Sprint 283
-
None
-
None
-
None
Description of problem:
Conformance test `[sig-node] Downward API should provide pod UID as env vars [NodeConformance] [Conformance]` fails sometimes with the following message: `message: 'Pod was rejected: Node didn''t have enough resource: cpu, requested: 250,used: 1000000000000245, capacity: 16000'` Which is completely unreasonable, as it amounts to 1 trillion CPUs and looks like an overflow.
Version-Release number of selected component (if applicable):
4.22
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-microshift-release-4.22-periodics-e2e-aws-ovn-ocp-conformance/2013203767624732672 https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-microshift-release-4.22-periodics-e2e-aws-ovn-ocp-conformance/2013175491632041984
Expected results:
Additional info:
- relates to
-
OCPBUGS-64847 Component Readiness: [Node / Kubelet] [FeatureGate:InPlacePodVerticalScaling] wrong calculation for used cpu
-
- POST
-
- links to