Bug 2071682

Summary:	sdn pod is crashing with panic: runtime error: invalid memory address or nil pointer dereference
Product:	OpenShift Container Platform	Reporter:	siva kanakala <skanakal>
Component:	Networking	Assignee:	Riccardo Ravaioli <rravaiol>
Networking sub component:	openshift-sdn	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	clasohm, ffernand, mfiedler, openshift-bugs-escalate, rravaiol
Version:	3.11.0
Target Milestone:	---
Target Release:	3.11.z
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-31 05:42:15 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 siva kanakala 2022-04-04 14:25:57 UTC

Description of problem:
sdn pod is crashing with the below error:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x3f69fd0]

Version-Release number of selected component (if applicable):
atomic-openshift-3.11.634-1.git.0.9b5be6d.el7.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
sdn pod always crashing with panic

Expected results:
sdn pod should be running 

Additional info:
sosreport attached on the case.

Comment 9 zhaozhanqi 2022-05-06 13:54:38 UTC

Verified this bug on 

# oc version
oc v3.11.694
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://zzhao311master-etcd-1:8443
openshift v3.11.694
kubernetes v1.11.0+d4cacc0

# oc get pod -n openshift-sdn
NAME        READY     STATUS    RESTARTS   AGE
ovs-54r9f   1/1       Running   0          4h
ovs-96jnq   1/1       Running   0          4h
ovs-g2bsk   1/1       Running   0          16m
ovs-n6t2j   1/1       Running   0          4h
sdn-7rnj7   1/1       Running   0          4h
sdn-822br   1/1       Running   0          16m
sdn-b2lfx   1/1       Running   0          4h
sdn-v7wtz   1/1       Running   0          4h

Comment 12 errata-xmlrpc 2022-05-31 05:42:15 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 3.11.705 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:2280