-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18, 4.19
-
?
-
Important
-
None
-
Rejected
-
False
-
-
Description of problem:
frr-k8s pods failing on nodes where VRFs are configured. From the frr container's log:
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()
Version-Release number of selected component (if applicable):
4.18.0-rc.9
metallb-operator.v4.18.0-202502041632
Steps to Reproduce:
1. Configuring symmetric routing by using VRFs with MetalLB. Use 1001 as route-table-id and configure VRF on top of vlan subinterface
2. Reboot nodes where VRF interface(s) is configured
3. Check frr-k8s status
Actual results:
frr-k8s pods in CrashLoopBackOff state
Expected results:
frr-k8s pods are running
Additional info:
Changing route-table-id to 999 seems to fix an issue
Affected Platforms:
- internal RedHat testing failure