-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.12
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The customer's workload was disrupted when rotating certificates for the pods controller-manager and route-controller-manager pod. (It seems to be certificates within client-ca)
Version-Release number of selected component (if applicable):
OCP 4.12
How the customer's workload works
- The pod named starting with 'scdf', 'scsf', 'absf', 'mf', 'absf' are receive ping from the pod named nats. - The nats pods accesses a connection state of other pods based on the latency of ping response. The nats pod sends ping to other pods every 500ms and it should repond within 1000 ms.
When the issue occured?
- The nats pod reported that there is a delay while pinging other pods. In other words, the the latency overs 1000ms. If you need more clarification for it, let the reporter know that. 2025-02-10 14:24:58.258526 2025-02-10 14:26:05.849588 2025-02-10 14:26:05.860654 2025-02-10 14:26:26.217602 2025-02-10 14:26:26.362595 2025-02-10 14:26:26.440514
How reproducible:
- Rotate certificates for the pods controller-manager and route-controller-manager pod while pods are pinging to each other in a pod network.
Steps to Reproduce:
1. pinging pods each other with the pod network.
2. Rotate certficates (client-ca) manually.
Additional information