-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
-
Followup item of ITN05 https://docs.google.com/document/d/1y2FT_JZi_iza5mU6eJHFPxlvvcG-IYPgxqBAJrI-0ME/edit
When hive pods error or complete, they are not automatically restarted, leaving some clusters stranded without a responsible hive pod.
oc get pods -n hive
NAME READY STATUS RESTARTS AGE
hive-clustersync-0 1/1 Running 0 3d12h
hive-clustersync-1 1/1 Running 0 3d12h
hive-clustersync-2 1/1 Running 0 18h
hive-clustersync-3 1/1 Running 0 35m
hive-clustersync-4 1/1 Running 0 3d12h
hive-clustersync-5 1/1 Running 0 3d12h
hive-clustersync-6 1/1 Running 0 3d12h
hive-clustersync-7 1/1 Running 0 3d12h
hive-clustersync-8 0/1 Completed 0 3d12h
hive-controllers-5d6c4d5c6-57726 1/1 Running 0 3d12h
hive-operator-6f7c445888-zlfts 1/1 Running 0 3d12h
hiveadmission-69b66b6dd8-b4cn5 1/1 Running 0 30h
hiveadmission-69b66b6dd8-qsnm5 1/1 Running 0 30h
Acceptance criteria:
hive pods automatically restart when they go into Completed or Error states
- relates to
-
HIVE-2399 [itn-2024-00005-followups] Clustersync pods intermittently have memory spikes
-
- In Progress
-
- links to
- mentioned on
