-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.19.z, 4.20.z, 4.21.z, 4.22
-
None
-
None
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
If one control plane node stays down, the OAS, OAuthAS pods cannot rotate.
This is found when verifying the OAuth pods OCPBUGS-65602.
Version-Release number of selected component (if applicable):
4.22
How reproducible:
Always
Steps to Reproduce:
1. Shut down a control plane node 2. Trigger the OAS pods and OAuthAS pods to rotate to a new revision. E.g. use oc edit openshiftapiserver/cluster authentication.operator/cluster to change to the logLevel to Debug and save. 3. Check the OAS pods and OAuthAS pods $ oc get po -n openshift-apiserver NAME READY STATUS RESTARTS AGE apiserver-586dd665d9-8g7r8 2/2 Running 0 5h19m apiserver-586dd665d9-btgvw 2/2 Running 0 5h17m apiserver-586dd665d9-vfsmw 2/2 Terminating 0 5h20m apiserver-9664f6db-n7hjt 0/2 Pending 0 28s $ oc get po -n openshift-oauth-apiserver NAME READY STATUS RESTARTS AGE apiserver-5b6585b776-vjjj2 0/1 Pending 0 74s apiserver-64cc7bbb6-czgfn 1/1 Terminating 0 5h19m apiserver-64cc7bbb6-tlk6s 1/1 Running 0 5h18m apiserver-64cc7bbb6-w7pmb 1/1 Running 0 5h20m
Actual results:
OAuth pods can rotate well to new revision as OCPBUGS-57444 fix. But OAS pods and OAuthAS pods can't. The new revision OAS apiserver-9664f6db-xxx pods and new revision OAuthAS apiserver-5b6585b776-xxx pods are NOT shown up Running.
Expected results:
Two replicas of the new revision OAS apiserver-9664f6db-xxx pods and new revision OAuthAS apiserver-5b6585b776-xxx pods are SHOWN up Running.
Additional info:
