Failing CI with FRR 10.0.1 - Tracker only!

[fedepaol]

This is only to track that CI is not stable when using FRR 10.0.1
I suspect this might be related to it requiring more resources from the runner (I tried the tests locally once and it seemed to work).

At the moment we are happy with 9.x, so there's no action to be taken for this issue.

[karampok]

Just as a note on the topic:

I have been testing the graceful restart test using the master tag for frr.
What I am observing is that

• without graceful restart
• with BFD
• establish once the BGP peering
• restart the frrk8s pods ( k delete pod)
• BGP is not re-established

Logs from the external peer

321 2024/11/07 14:16:55.650 BGP: [NJ2F2-2W769] 172.18.0.2 [Event] BGP connection closed fd 23
322 2024/11/07 14:16:55.650 BGP: [NTX3S-9Q8YV] 172.18.0.2 [Event] BGP error 5 on fd 23
323 2024/11/07 14:16:55.650 BGP: [ZWCSR-M7FG9] 172.18.0.2 [FSM] TCP_connection_closed (Established->Clearing), fd 23
324 2024/11/07 14:16:55.650 BGP: [V4R0W-D4WGF] 172.18.0.2(Unknown) Update Group Hash: sort: 1 sub_sort: 0 UpdGrpFlags: 0 UpdGrpAFFlags: 553648135
325 2024/11/07 14:16:55.650 BGP: [NVVBY-K8MCE] 172.18.0.2(Unknown) Update Group Hash: addpath: 4 UpdGrpCapFlag: 256 UpdGrpCapAFFlag: 2048 route_adv: 0 change local as:       ↻ 0, as_path_loop_detection: 0
326 2024/11/07 14:16:55.650 BGP: [X4CQ0-63QKB] 172.18.0.2(Unknown) Update Group Hash: addpath paths-limit: (send 0, receive 0)
327 2024/11/07 14:16:55.650 BGP: [Z8Q37-65KK3] 172.18.0.2(Unknown) Update Group Hash: max packet size: 4096 pmax_out: 0 Peer Group: (NONE) rmap out: (NONE)
328 2024/11/07 14:16:55.650 BGP: [SM2F3-HRYKP] 172.18.0.2(Unknown) Update Group Hash: dlist out: (NONE) plist out: (NONE) aslist out: (NONE) usmap out: (NONE) advmap:        ↻ (NONE) 0
329 2024/11/07 14:16:55.650 BGP: [V8B3M-T6VFC] 172.18.0.2(Unknown) Update Group Hash: default rmap: (NONE) shared network and afi active network: 0
330 2024/11/07 14:16:55.650 BGP: [Y5EX3-GHT5V] 172.18.0.2(Unknown) Update Group Hash: Lonesoul: 0 ORF prefix: 0 max prefix out: 0
331 2024/11/07 14:16:55.650 BGP: [X19K7-9V4K2] 172.18.0.2(Unknown) Update Group Hash: local role: 255 AIGP: 0 SOO: (NONE)
332 2024/11/07 14:16:55.650 BGP: [JW3N0-RCE28] 172.18.0.2(Unknown) Update Group Hash: IPv6 nexthop-local unchanged: 0 IPv6 global fc00:f853:ccd:e793::3
333 2024/11/07 14:16:55.650 BGP: [SQ314-QBJCR] 172.18.0.2(Unknown) Update Group Hash key: 3032603789
334 2024/11/07 14:16:55.650 BGP: [T91AW-FGMHW] bgp_fsm_change_status : vrf default(0), Status: Clearing established_peers 0
335 2024/11/07 14:16:55.650 BGP: [HKWM3-ZC5QP] 172.18.0.2 fd -1 went from Established to Clearing
336 2024/11/07 14:16:55.660 BGP: [ZWCSR-M7FG9] 172.18.0.2 [FSM] Clearing_Completed (Clearing->Idle), fd -1
337 2024/11/07 14:16:55.660 BGP: [T91AW-FGMHW] bgp_fsm_change_status : vrf default(0), Status: Idle established_peers 0
338 2024/11/07 14:16:55.660 BGP: [HKWM3-ZC5QP] 172.18.0.2 fd -1 went from Clearing to Idle
339 2024/11/07 14:16:55.710 BGP: [KPK7M-B9FAF] BGP withdrawing  route 192.168.2.0/24(VRF default) with dest 0x7fba105a8d00 and flags 0x800 to zebra
340 2024/11/07 14:16:55.710 BGP: [W7M9T-Y0DGM] Tx route delete VRF default (table id 0) 192.168.2.0/24
341 2024/11/07 14:16:55.720 ZEBRA: [HA0PY-0J478] rib_delnode: (default:254):192.168.2.0/24: rn 0x7fe01546bc10, re 0x7fe01546dab0, removing
342 2024/11/07 14:16:55.720 ZEBRA: [X8377-PYAKV] (default:254):192.168.2.0/24: Redist del: re 0x7fe01546dab0 (0:bgp), new re 0x0 (0:None)
343 2024/11/07 14:16:55.720 ZEBRA: [S59C1-4C5PP] default(0:254):192.168.2.0/24: Deleting route rn 0x7fe01546bc10, re 0x7fe01546dab0 (bgp)
344 2024/11/07 14:16:55.720 ZEBRA: [HZ7BM-3P3HS] rib_process: (default:254):192.168.2.0/24: rn 0x7fe01546bc10, removing re 0x7fe01546dab0
345 2024/11/07 14:16:55.720 ZEBRA: [XDKQQ-BJZ0M] rib_unlink: (default:254):192.168.2.0/24: rn 0x7fe01546bc10, re 0x7fe01546dab0
346 2024/11/07 14:16:55.720 ZEBRA: [J1MXG-0722F] rib_gc_dest: (default:?):192.168.2.0/24: removing dest from table
347 2024/11/07 14:16:55.721 ZEBRA: [YXPF5-B2CE0] netlink_route_multipath_msg_encode: RTM_DELROUTE 192.168.2.0/24 vrf 0(254)
348 2024/11/07 14:16:55.721 ZEBRA: [HYEHE-CQZ9G] nl_batch_send: netlink-dp (NS 0), batch size=44, msg cnt=1
349 2024/11/07 14:16:56.492 BFD: [SEY1D-NT8EQ] state-change: [mhop:no peer:172.18.0.2 local:172.18.0.3 vrf:default ifname:eth0] up -> down reason:control-expired
350 2024/11/07 14:16:56.493 ZEBRA: [V0KXZ-QFE4D] bfd_dst_update msg from client bfd: length=25
351 2024/11/07 14:16:56.495 BGP: [Q4BCV-6FHZ5] zclient_bfd_session_update: 172.18.0.3/32 -> 172.18.0.2/32 (interface eth0) VRF default(0) (CPI bit no): Down
352 2024/11/07 14:16:56.495 BGP: [MKVHZ-7MS3V] bfd_session_status_update: neighbor 172.18.0.2 vrf default(0) bfd state Up -> Down
353 2024/11/07 14:16:56.495 BGP: [QFMSE-NPSNN] zclient_bfd_session_update:   sessions updated: 1
354 2024/11/07 14:16:59.390 ZEBRA: [KMXEB-K771Y] netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=76, seq=0, pid=0
355 2024/11/07 14:16:59.390 ZEBRA: [TDS34-MNEJW]     Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring
356 2024/11/07 14:16:59.390 ZEBRA: [KKAC1-JMWTB] Rx RTM_NEWNEIGH family ipv4 IF eth0(1952) vrf default(0) IP 172.18.0.2 MAC 02:42:ac:12:00:02 state 0x2 flags 0x0             ↻ ext_flags 0x0
357 2024/11/07 14:17:07.381 BGP: [ZGYKZ-X9JJR] 172.18.0.2 - incoming conn rejected - no AF activated for peer

[65278]

I'll chime in here.
I have a usecase for >=FRR 10.2. I'm trying to use the lua scripting host to extend some functionality of FRR, but I can't because of a bug: FRRouting/frr#16900
In short, the global namespace is lost, and therefore no non-core functions can be used.
This isn't urgent, but I'll eventually make a proposal to support scripting.

[fedepaol]

Yes we are trying to get back on track and support a newer frr version. It just will take some time as we need to understadn / narrow down if something is not working.

[65278]

Since the fix is small, I can offer to backport it for the frr guys. I'll inquire about that.