-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
4.19.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Long running commands oc exec and oc rsh are terminated prematurely with 0 exit code during OCP cluster upgrade
Version-Release number of selected component (if applicable):
Client Version: 4.19.0 Kustomize Version: v5.5.0 Server Version: 4.19.6 Kubernetes Version: v1.32.7
How reproducible:
Always
Steps to Reproduce:
1.Install OCP 4.19.6 2.start `oc exec -n openshift-monitoring prometheus-k8s-0 -- sleep 99999` or use any other pod 3.Start cluster upgrade process to 4.19.9
Actual results:
oc exec is terminated prematurely with 0 exit code during OCP cluster upgrade
Expected results:
oc exec should exit with exit code > 0
Additional info:
Both oc exec and oc rsh are affected. I tried to find a smaller reproducer e.g. applying ImageDigestMirrorSet resource which triggers cluster reconciliation but in that case the commend exits as expected with: "command terminated with exit code 137"