Multiple co degraded after master node replacement in RHOCP 4

Solution Verified - Updated -

Issue

  • Observed multiple CO degraded after node replacement.
  • During master node replacement, older master node came up caused CO degrade issue.
authentication                             4.14.17   False       True          True       39h     APIServicesAvailable: "oauth.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request...
kube-apiserver                             4.14.17   True        True          True       593d    TargetConfigControllerDegraded: "serviceaccount/localhost-recovery-client": Internal error occurred: no matching key was found for the provided AES transformer
kube-controller-manager                    4.14.17   True        False         True       593d    TargetConfigControllerDegraded: "serviceaccount/localhost-recovery-client": Internal error occurred: no matching key was found for the provided AES transformer
kube-scheduler                             4.14.17   True        False         True       593d    TargetConfigControllerDegraded: "serviceaccount/localhost-recovery-client": Internal error occurred: no matching key was found for the provided AES transformer

Environment

  • Red Hat Openshift Container Platform (RHOCP) 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content