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

Bug 1818182

Summary: KubePodCrashLooping: Pod openshift-sdn/sdn-zbc27
Product: OpenShift Container Platform Reporter: Hongkai Liu <hongkliu>
Component: NetworkingAssignee: Ben Bennett <bbennett>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED DUPLICATE Docs Contact:
Severity: unspecified    
Priority: unspecified    
Version: 4.3.0   
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-03-30 14:39:06 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:
Attachments:
Description Flags
sdn-zbc27.log
none
ovs-vf24q.log none

Description Hongkai Liu 2020-03-27 22:46:59 UTC 
Created attachment 1674193 [details]
sdn-zbc27.log

Description of problem:
[FIRING:1] KubePodCrashLooping kube-state-metrics (sdn https-main 10.129.64.17:8443 openshift-sdn sdn-zbc27 openshift-monitoring/k8s kube-state-metrics critical)
Pod openshift-sdn/sdn-zbc27 (sdn) is restarting 0.42 times / 5 minutes.

AlertManager fired the above one this afternoon.

https://coreos.slack.com/archives/CHY2E1BL4/p1585335910021700

What caused the restarts/CrashLooping?
Should we do anything when such an alert happens?

Version-Release number of selected component (if applicable):
oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.3.0-0.nightly-2020-03-23-130439   True        False         3d9h    Cluster version is 4.3.0-0.nightly-2020-03-23-130439

How reproducible:
Saw it once

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
The previous pod log (sdn-zbc27.log) is attached.

oc get pod -n openshift-sdn -o wide | grep ip-10-0-138-234.ec2.internal
ovs-vf24q              1/1     Running   1          3d10h   10.0.138.234   ip-10-0-138-234.ec2.internal   <none>           <none>
sdn-zbc27              1/1     Running   4          3d10h   10.0.138.234   ip-10-0-138-234.ec2.internal   <none>           <none>
Comment 1 Hongkai Liu 2020-03-27 22:48:08 UTC 
Created attachment 1674194 [details]
ovs-vf24q.log
Comment 2 Ben Bennett 2020-03-30 14:39:06 UTC 

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