-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.12.z
-
No
-
SDN Sprint 244, SDN Sprint 245, SDN Sprint 246
-
3
-
Rejected
-
False
-
-
Service Delivery Architecture Overview
Description of problem:
ovs-vswitchd process on worker nodes service HCP components have very high CPU usage.
Version-Release number of selected component (if applicable):
4.12.
How reproducible:
This has only been seen on HyperShift worker nodes. Root cause is believed to be Egress policies which define exceptions via CIDR ranges or port ranges, ie: spec: podSelector: matchLabels: role: db policyTypes: - Ingress - Egress ingress: - from: - ipBlock: cidr: 172.17.0.0/16 except: - 172.17.1.0/24 OR spec: podSelector: matchLabels: role: db policyTypes: - Egress egress: - to: - ipBlock: cidr: 10.0.0.0/24 ports: - protocol: TCP port: 32000 endPort: 32768
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
This was seen during an incident mentioned in the releated OHSS ticket
- is blocked by
-
OCPBUGS-17120 [release-4.13] 4.13.z FIPS build - HyperShift - pods crashlooping with API connection failures
- Closed
-
OCPBUGS-24263 [release-4.13] High CPU usage in the ovs-vswitchd daemon
- Closed
- is cloned by
-
OCPBUGS-24263 [release-4.13] High CPU usage in the ovs-vswitchd daemon
- Closed
- is related to
-
SDN-4194 Define alerts for high OVS CPU usage
- Closed
- links to
-
RHBA-2023:7823 OpenShift Container Platform 4.12.z bug fix update
-
RHBA-2024:0198 OpenShift Container Platform 4.12.z bug fix update