Description of problem:  routes of pod network on default network are not cleaned up on hypervisor after frrconfiguration, ra configurations and external frr container were all deleted

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

How reproducible:

Steps to Reproduce:

1.  at end of Feb 19, I was running some automated legacy egressIP on BGP default network, during the test, I observed, default pod network was advertised correctly (although EIP was not advertised due to  ), egressIP itself also worked.  After the test, frrconfiguration, RA and external frr container were all deleted.

2. on Feb 20 morning, I noticed pod network routes are still on hypervisor although there is no BGP configured 

[root@sdn-09 ~]# oc get frrconfiguration -A
No resources found
[root@sdn-09 ~]# oc get ra -A
No resources found
[root@sdn-09 ~]# sudo podman ps | grep frr
[root@sdn-09 ~]# 
[root@sdn-09 ~]# ip route show|grep bgp
10.128.0.0/23 nhid 10120 via 192.168.111.20 dev offloadbm proto bgp metric 20 
10.128.2.0/23 nhid 10124 via 192.168.111.23 dev offloadbm proto bgp metric 20 
10.129.0.0/23 nhid 10123 via 192.168.111.21 dev offloadbm proto bgp metric 20 
10.129.2.0/23 nhid 10125 via 192.168.111.25 dev offloadbm proto bgp metric 20 
10.130.0.0/23 nhid 10121 via 192.168.111.22 dev offloadbm proto bgp metric 20 
10.131.0.0/23 nhid 10122 via 192.168.111.24 dev offloadbm proto bgp metric 20 

Actual results: advertised pod network routes are not cleaned up

Expected results: advertised pod network routes should be cleaned up afte BGP configuration are all after all

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