-
Bug
-
Resolution: Done-Errata
-
Blocker
-
None
-
None
-
frr-7.5.1-22.el8
-
None
-
None
-
ZStream
-
rhel-sst-cs-net-perf-services
-
ssg_core_services
-
26
-
None
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
Approved Blocker
-
Pass
-
RegressionOnly
-
None
What were you trying to do that didn't work?
FRR not initiating BGP connection with the external neighbor
Please provide the package NVR for which bug is seen:
rpm -q frr
frr-7.5-11.el8_6.5.x86_64
How reproducible:
Comes from a customer case. MetalLB bug is https://issues.redhat.com/browse/OCPBUGS-27425
Steps to reproduce
Expected results
Actual results
Zebra prints out:
2024-01-16T17:04:01.701723737+00:00 stdout F 2024/01/16 17:04:01.701 ZEBRA: rnh_register msg from client bgp: hdr->length=8, type=nexthop vrf=0 2024-01-16T17:04:01.701723737+00:00 stdout F 2024/01/16 17:04:01.701 ZEBRA: 0: Add RNH 10.145.255.254/32 type Nexthop 2024-01-16T17:04:01.701723737+00:00 stdout F 2024/01/16 17:04:01.701 ZEBRA: 0:10.145.255.254/32: Evaluate RNH, type Nexthop (force) 2024-01-16T17:04:01.701723737+00:00 stdout F 2024/01/16 17:04:01.701 ZEBRA: 0:10.145.255.254/32: NH has become unresolved
The neigh status prints
Connections established 0; dropped 0
Last reset 2d11h45m, Waiting for NHT
External BGP neighbor may be up to 255 hops away.
Also:
Output of - oc -n metallb-system exec -it speaker-xxxxx -c frr -- vtysh -c "show ip bgp 10.145.255.254" [core@bastion-spoke ~]$ oc -n metallb-system exec -it speaker-28t57 -c frr -- vtysh -c "show ip bgp 10.145.255.254" % Network not in table [core@bastion-spoke ~]$ oc -n metallb-system exec -it speaker-28t57 -c frr -- vtysh -c "show ip nht" 10.145.255.254 unresolved Client list: bgp(fd 15)
When FRR starts, we see the following logs :
2024-01-16T17:46:33.605673760+00:00 stderr F 2024/01/16 17:46:33 ZEBRA: [EC 4043309092] netlink-cmd (NS 0) error: data remnant size 32336 2024-01-16T17:46:33.605673760+00:00 stderr F 2024/01/16 17:46:33 ZEBRA: [EC 4043309092] netlink-cmd (NS 0) error: data remnant size 32768
This looks similar to https://github.com/FRRouting/frr/issues/10404 but it's missing the third line on the issue.
I am attaching the frr logs but attached to the case there's also the sos report in case it's needed.
Also, I am attaching the output of frr running-conf too.
- links to
-
RHSA-2023:122193
frr bug fix and enhancement update
- mentioned on
