Description of problem:

ovnkube carshed when recreated with egressip enabled

 
E1122 08:50:12.920452   42037 nad_controller.go:335] Giving egress ip nodes map[worker-2:[default]] for network default
I1122 08:50:12.920488   42037 external_controller_pod.go:21] APB queuing policies: map[] for pod: openshift-machine-api/metal3-baremetal-operator-5897cd5c67-vw4bd
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1e8bb35]
 
goroutine 1098 [running]:
github.com/ovn-org/ovn-kubernetes/go-controller/pkg/retry.(*RetryFramework).DoWithLock(0x0, {0xc000808d40, 0xd}, 0xc001a15c88)
/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/retry/obj_retry.go:135 +0x35
github.com/ovn-org/ovn-kubernetes/go-controller/pkg/retry.(*RetryFramework).AddRetryObjWithAddNoBackoff(0x0, {0x28a8d80, 0xc001542300})
/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/retry/obj_retry.go:195 +0x11f
github.com/ovn-org/ovn-kubernetes/go-controller/pkg/ovn.(*egressIPZoneController).reconcileNetwork(0xc0016b4cd8, {0x291356b, 0x7})
/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/ovn/egressip.go:2460 +0x2f9
github.com/ovn-org/ovn-kubernetes/go-controller/pkg/controller.(*controller[...]).processNextQueueItem(0x7272456e4f73676f)
/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/controller/controller.go:253 +0xd7
github.com/ovn-org/ovn-kubernetes/go-controller/pkg/controller.(*controller[...]).startWorkers.func1()
/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/controller/controller.go:163 +0x6f
created by github.com/ovn-org/ovn-kubernetes/go-controller/pkg/controller.(*controller[...]).startWorkers in goroutine 117
/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/controller/controller.go:160 +0x185
 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1. Setup cluster and enable routeAdvertisements

2.  Create egressip resource and make node assigned

3.  recreate ovnkube pod 

Actual results:

Expected results:

Additional info:

Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.

Affected Platforms:

Is it an

1. internal CI failure
2. customer issue / SD
3. internal RedHat testing failure

If it is an internal RedHat testing failure:

• Please share a kubeconfig or creds to a live cluster for the assignee to debug/troubleshoot along with reproducer steps (specially if it's a telco use case like ICNI, secondary bridges or BM+kubevirt).

If it is a CI failure:

• Did it happen in different CI lanes? If so please provide links to multiple failures with the same error instance
• Did it happen in both sdn and ovn jobs? If so please provide links to multiple failures with the same error instance
• Did it happen in other platforms (e.g. aws, azure, gcp, baremetal etc) ? If so please provide links to multiple failures with the same error instance
• When did the failure start happening? Please provide the UTC timestamp of the networking outage window from a sample failure run
• If it's a connectivity issue,
• What is the srcNode, srcIP and srcNamespace and srcPodName?
• What is the dstNode, dstIP and dstNamespace and dstPodName?
• What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)

If it is a customer / SD issue:

• Provide enough information in the bug description that Engineering doesn’t need to read the entire case history.
• Don’t presume that Engineering has access to Salesforce.
• Do presume that Engineering will access attachments through supportshell.
• Describe what each relevant attachment is intended to demonstrate (failed pods, log errors, OVS issues, etc).
• Referring to the attached must-gather, sosreport or other attachment, please provide the following details:
  • If the issue is in a customer namespace then provide a namespace inspect.
  • If it is a connectivity issue:
    • What is the srcNode, srcNamespace, srcPodName and srcPodIP?
    • What is the dstNode, dstNamespace, dstPodName and dstPodIP?
    • What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)
    • Please provide the UTC timestamp networking outage window from must-gather
    • Please provide tcpdump pcaps taken during the outage filtered based on the above provided src/dst IPs
  • If it is not a connectivity issue:
    • Describe the steps taken so far to analyze the logs from networking components (cluster-network-operator, OVNK, SDN, openvswitch, ovs-configure etc) and the actual component where the issue was seen based on the attached must-gather. Please attach snippets of relevant logs around the window when problem has happened if any.

• When showing the results from commands, include the entire command in the output.  
• For OCPBUGS in which the issue has been identified, label with “sbr-triaged”
• For OCPBUGS in which the issue has not been identified and needs Engineering help for root cause, label with “sbr-untriaged”
• Do not set the priority, that is owned by Engineering and will be set when the bug is evaluated
• Note: bugs that do not meet these minimum standards will be closed with label “SDN-Jira-template”
• For guidance on using this template please see
  OCPBUGS Template Training for Networking  components