-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
x86_64
-
None
-
None
-
Rejected
-
CORENET Sprint 277, CORENET Sprint 278
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem: When comparing CPU utilization of the ovs-vswitchd vs the 4.19.0 baseline it shows increased CPU utilization that is above the acceptable and agreed upon threshold of 20%
Version-Release number of selected component (if applicable): 4.20.0-ec.6
How reproducible:
Steps to Reproduce:
1. Deploy SNO cluster
2. Run workload for 12hr
3. Observe CPU utilization over the 12hr period
Actual results:
/ovs.slice/ovs-vswitchd.service _ daemon-> current: 0.0207041 baseline: 0.0136625 deviation: 51.54%
Expected results:
CPU increase below 20%
Additional info:
Affected Platforms: Baremetal SPR-EE
Is it an
- internal RedHat testing failure
If it is an internal RedHat testing failure:
- Please share a kubeconfig or creds to a live cluster for the assignee to debug/troubleshoot along with reproducer steps (specially if it's a telco use case like ICNI, secondary bridges or BM+kubevirt).
I can reproduce the issue and provide access to the cluster