-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.14.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
None
-
None
-
None
-
None
-
OCP Node Sprint 278 (green)
-
1
-
Customer Escalated
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
We have deployed SNO with version 4.14 on HP BareMetal server. On top of OpenShift deployed our application in which we noticed there is multiple API request timeout last week June 14 around 11:00 AM UTC to 12:30 PM IST. We need RH to investigate this issue and find root cause for this issue.
Version-Release number of selected component (if applicable):
How reproducible:
this is not reproducible in our environment but happening on customer's environment
Steps to Reproduce:
After deep logs investigation we found that the OpenShift Api server went down 6 times in last months. For fourt times 01.07.2025, 26.07.2025, 17.07.2025 and 10.07.2025 the restart and recovered in less than 30 seconds. But on 14-07-2025 the recovery took very long time to recover openshift-api server. 2025-07-14T11:15 – 2025-07-14T11:33 ---> 18 minutes 2025-07-14T11:54 – 2025-07-14T12:14 ---> 20 minutes 2025-07-14T12:55 – 2025-07-14T13:28 ---> 33 minutes Then on 16-07-2025 the recovery took almost 40 minutes 2025-07-15T23:16 - 2025-07-15T23:55 – 39 minutes 2025-07-16T00:16 - 2025-07-16T00:17 – 1 minute please help us to know why the recovery took such a long time and the restarts are very random unlike you mentioned for every days.
Actual results:
Expected results:
Additional info:
- relates to
-
OCPBUGS-59153 Static pods should start after being created [openshift-etcd]
-
- New
-