What were you trying to do that didn't work?

Due to a bad interaction between ovn-kubernetes, a VRF we had a bgp session over was removed from the host network namespace.

This caused frr to crash.

 
2025/02/14 10:55:05.426 BFD: [VCGF0-X62M1][EC 100663301] INTERFACE_STATE: Cannot find IF bond0.357vrf in VRF 230
2025/02/14 10:55:05.426 BFD: [VCGF0-X62M1][EC 100663301] INTERFACE_STATE: Cannot find IF bond0.357vrf in VRF 230
2025/02/14 10:55:05.426 STATIC: [VCGF0-X62M1][EC 100663301] INTERFACE_STATE: Cannot find IF bond0.357vrf in VRF 230
2025/02/14 10:55:05.426 BFD: [YNQCS-MR20J][EC 100663301] INTERFACE_VRF_UPDATE: Cannot find IF bond0.357vrf in VRF 230
2025/02/14 10:55:05.426 STATIC: [VCGF0-X62M1][EC 100663301] INTERFACE_STATE: Cannot find IF bond0.357vrf in VRF 230
2025/02/14 10:55:05.426 BGP: [VCGF0-X62M1][EC 100663301] INTERFACE_STATE: Cannot find IF bond0.357vrf in VRF 230
ZEBRA: Received signal 11 at 1739530505 (si_addr 0x31, PC 0x55f84a91c0cd); aborting...
ZEBRA: /usr/lib64/frr/libfrr.so.0(zlog_backtrace_sigsafe+0x71) [0x7ff95c21bb01]
ZEBRA: /usr/lib64/frr/libfrr.so.0(zlog_signal+0xf5) [0x7ff95c21bd05]
ZEBRA: /usr/lib64/frr/libfrr.so.0(+0xcf465) [0x7ff95c244465]
ZEBRA: /lib64/libc.so.6(+0x3e6f0) [0x7ff95bf796f0]
ZEBRA: /usr/libexec/frr/zebra(+0xe80cd) [0x55f84a91c0cd]
ZEBRA: /usr/lib64/frr/libfrr.so.0(work_queue_run+0x88) [0x7ff95c25b588]
ZEBRA: /usr/lib64/frr/libfrr.so.0(thread_call+0x81) [0x7ff95c254b71]
ZEBRA: /usr/lib64/frr/libfrr.so.0(frr_run+0xe8) [0x7ff95c2173c8]
ZEBRA: /usr/libexec/frr/zebra(main+0x386) [0x55f84a8b7366]
ZEBRA: /lib64/libc.so.6(+0x29590) [0x7ff95bf64590]
ZEBRA: /lib64/libc.so.6(__libc_start_main+0x80) [0x7ff95bf64640]
ZEBRA: /usr/libexec/frr/zebra(_start+0x25) [0x55f84a8b7a55]
ZEBRA: in thread work_queue_run scheduled from lib/workqueue.c:136 work_queue_schedule()

What is the impact of this issue to you?

Please provide the package NVR for which the bug is seen:

frr-8.5.3-4.el9.x86_64

SOS report: https://file.emea.redhat.com/~yprokule/SOSReports/OCP/OCPBUGS-50855/

How reproducible is this bug?:

It was consistent in CI

Steps to reproduce

Expected results

No crash

Actual results