Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1835375

Summary: kube-apiserver: \"kube-apiserver\" is not ready: CrashLoopBackOff: back-off
Product: OpenShift Container Platform Reporter: Kirsten Garrison <kgarriso>
Component: kube-apiserverAssignee: Stefan Schimanski <sttts>
Status: CLOSED DUPLICATE QA Contact: Xingxing Xia <xxia>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, mfojtik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-19 09:43:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kirsten Garrison 2020-05-13 17:26:00 UTC
MCO is seeing failed CI runs consistently and am seeing in thse runs many occurances of:
```
I0513 15:10:43.158175       1 event.go:278] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-kube-apiserver-operator", Name:"kube-apiserver-operator", UID:"df0bd87a-a0e2-416d-8b8d-99c1b01416eb", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'OperatorStatusChanged' Status for clusteroperator/kube-apiserver changed: Degraded message changed from "StaticPodsDegraded: pod/kube-apiserver-ci-op-wmnxm-m-2.c.openshift-gce-devel-ci.internal container \"kube-apiserver\" is not ready: CrashLoopBackOff: back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-ci-op-wmnxm-m-2.c.openshift-gce-devel-ci.internal_openshift-kube-apiserver(76f10270a448a03ef9ada0576a707358)\nStaticPodsDegraded: pod/kube-apiserver-ci-op-wmnxm-m-2.c.openshift-gce-devel-ci.internal container \"kube-apiserver\" is waiting: CrashLoopBackOff: back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-ci-op-wmnxm-m-2.c.openshift-gce-devel-ci.internal_openshift-kube-apiserver(76f10270a448a03ef9ada0576a707358)\nNodeControllerDegraded: All master nodes are ready" to "StaticPodsDegraded: pod/kube-apiserver-ci-op-wmnxm-m-2.c.openshift-gce-devel-ci.internal container \"kube-apiserver\" is not ready: unknown reason\nNodeControllerDegraded: All master nodes are ready"
```

In the below log that Crashloop backoff occurs 189 times when I search.. This doesn't seem normal to me?

https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1728/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/2214/artifacts/e2e-gcp-op/pods/openshift-kube-apiserver-operator_kube-apiserver-operator-d59d9b6f8-v8nqc_kube-apiserver-operator.log

Another set of logs:
https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1724/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/2215/artifacts/e2e-gcp-op/pods/openshift-kube-apiserver-operator_kube-apiserver-operator-75bf798cc5-v54cq_kube-apiserver-operator.log

Comment 1 Stefan Schimanski 2020-05-19 09:43:18 UTC

*** This bug has been marked as a duplicate of bug 1828606 ***