Bug 2094039

Summary: egressIP panics with nil pointer dereference
Product: OpenShift Container Platform Reporter: Surya Seetharaman <surya>
Component: NetworkingAssignee: Surya Seetharaman <surya>
Networking sub component: ovn-kubernetes QA Contact: huirwang
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: huirwang
Version: 4.8   
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2105653 (view as bug list) Environment:
Last Closed: 2022-08-10 11:16:21 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:
Bug Depends On:    
Bug Blocks: 2079012, 2105653, 2105657    

Description Surya Seetharaman 2022-06-06 16:11:57 UTC
Description of problem:


E0606 11:57:34.063567       1 egressip.go:2096] Node: huirwang-0606c-m5w24-worker-2-dkjmc reachability changed, but could not retrieve node from cache, err: node "huirwang-0606c-m5w24-worker-2-dkjmc" not found
W0606 11:57:34.063658       1 egressip.go:1657] Unable to remove GARP configuration on external logical switch port for egress node: huirwang-0606c-m5w24-worker-2-dkjmc, err: object not found
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x176626d]

goroutine 487 [running]:
github.com/ovn-org/ovn-kubernetes/go-controller/pkg/ovn.(*Controller).checkEgressNodesReachability(0xc000171c00)
	/home/surya/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/ovn/egressip.go:2099 +0x3ed
created by github.com/ovn-org/ovn-kubernetes/go-controller/pkg/ovn.(*Controller).initClusterEgressPolicies
	/home/surya/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/ovn/egressip.go:1772 +0xdb
,StartedAt:2022-06-06 07:15:01 +0000 UTC,FinishedAt:2022-06-06 11:57:34 +0000 UTC,ContainerID:cri-o://fba01e1128db4bffabbb8cfeeea83e19ef7cf00f3fc6427a540e122e2d0a43d9,},},Ready:true,RestartCount:3,Image:quay.io/itssurya/dev-images:e5a4884b-83c7-4728-9117-936093a25c7d,ImageID:quay.io/itssurya/dev-images@sha256:507c9739c49dd0f8590ddee5da2f4974fa5f0af6842cb592c8203617c92f33f5,ContainerID:cri-o://59b48c5c5d299c185951e873c1f33f2ad53367d9be8f5821186ee1c46f1da841,Started:*true,},ContainerStatus{Name:sbdb,State:ContainerState{Waiting:nil,Running:&ContainerStateRunning{StartedAt:2022-06-06 06:47:44 +0000 UTC,},Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:true,RestartCount:0,Image:quay.io/itssurya/dev-images:e5a4884b-83c7-4728-9117-936093a25c7d,ImageID:quay.io/itssurya/dev-images@sha256:507c9739c49dd0f8590ddee5da2f4974fa5f0af6842cb592c8203617c92f33f5,ContainerID:cri-o://


Version-Release number of selected component (if applicable):
Seen on 4.11.nightly, yet to determine how far we might need to backport this.


How reproducible:


Steps to Reproduce:
1. same as mentioned https://bugzilla.redhat.com/show_bug.cgi?id=2079012#c19
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 errata-xmlrpc 2022-08-10 11:16:21 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 4.11.0 bug fix and 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:5069