openshift-apiserver operator repeatedly moves from True to False after certificate recovery
Issue
- After executing disaster recovery steps and creating a backup API, the openshift-apiserver operator is flapping between True and False in the available column:
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE
authentication 4.2.20 True False False 40d
cloud-credential 4.2.20 True False False 290d
cluster-autoscaler 4.2.20 True False False 290d
console 4.2.20 True False False 10d
dns 4.2.20 True True False 290d
image-registry 4.2.20 True False False 30d
ingress 4.2.20 True False False 289d
insights 4.2.20 True False False 172d
kube-apiserver 4.2.20 True False False 290d
kube-controller-manager 4.2.20 True False False 290d
kube-scheduler 4.2.20 True False False 290d
machine-api 4.2.20 True False False 290d
machine-config 4.2.20 True False False 4d13h
marketplace 4.2.20 True False False 10d
monitoring 4.2.20 False True True 7s
network 4.2.20 True False False 290d
node-tuning 4.2.20 True False False 10d
openshift-apiserver 4.2.20 False False False 10s
openshift-controller-manager 4.2.20 True False False 10d
openshift-samples 4.2.20 True False False 73d
operator-lifecycle-manager 4.2.20 True False False 162d
operator-lifecycle-manager-catalog 4.2.20 True False False 162d
operator-lifecycle-manager-packageserver 4.2.20 True False False 10m
service-ca 4.2.20 True False False 290d
service-catalog-apiserver 4.2.20 True False False 3m26s
service-catalog-controller-manager 4.2.20 True False False 10d
storage 4.2.20 True False False 29d
- This is resulting in login intermittency and general cluster instability.
Environment
- OpenShift Container Platform
- 4.2
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.