-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.17, 4.18, 4.19
-
Yes
-
Approved
-
False
-
-
Release Note Not Required
-
In Progress
This is a clone of issue OCPBUGS-49613. The following is the description of the original issue:
—
Description of problem:
Note this is without UDN
While tracking nightly runs we see that there is a big jump in CPU utilization between 4.18.0-0.nightly-2025-01-28-114040 and 4.18.0-0.nightly-2025-01-28-165333 nightliesÂ
andÂ
4.19.0-0.nightly-2025-01-25-021606 and 4.19.0-0.nightly-2025-01-27-130640
nightlies
which corresponds to https://github.com/openshift/ovn-kubernetes/pull/2426 https://github.com/openshift/ovn-kubernetes/pull/2420 PRs being merged
Version-Release number of selected component (if applicable): 4.18 and 4.19
How reproducible:
Always
Steps to Reproduce:
1. Run node-density and check ovnkube-controller cpu usage
Actual results:
Worse CPU utilization
Expected results:
Similar or better CPU utilization
- blocks
-
CNV-54728 Performance upgrade testing for 4.18.0
-
- In Progress
-
-
TRT-2002 4.18.0-rc.9 selection
-
- Closed
-
- clones
-
OCPBUGS-49613 Significant increase in average ovnkube-controller cpu usage between two nightlies
-
- Verified
-
- is blocked by
-
OCPBUGS-49613 Significant increase in average ovnkube-controller cpu usage between two nightlies
-
- Verified
-
- is duplicated by
-
OCPBUGS-48760 Test flaking frequently in both 4.18 and 4.19 "[sig-network] pods should successfully create sandboxes by other "
-
- Closed
-
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update