-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.17
-
None
-
Moderate
-
Yes
-
False
-
-
Description of problem:
Failed to collect BGP and BFD as it was before:
oc exec -it frr-k8s-kmpdn -n metallb-system -c frr-metrics -- sh sh-5.1# curl localhost:29151/metrics curl: (7) Failed to connect to localhost port 29151: Connection refused
Version-Release number of selected component (if applicable):
Server Version: 4.17.0-ec.3
metallb-operator.v4.17.0-202408121444
How reproducible:
100%
Steps to Reproduce:
1. Connect to the frr-pod
2. try to curl metrics via old(29151) or new port (7572)
3.
Actual results:
No bgp or bfd metric
Expected results:
# HELP metallb_bfd_control_packet_input Number of received BFD control packets # TYPE metallb_bfd_control_packet_input counter metallb_bfd_control_packet_input{peer="10.46.186.88",vrf="default"} 133 # HELP metallb_bfd_control_packet_output Number of sent BFD control packets # TYPE metallb_bfd_control_packet_output counter metallb_bfd_control_packet_output{peer="10.46.186.88",vrf="default"} 134 # HELP metallb_bfd_echo_packet_input Number of received BFD echo packets # TYPE metallb_bfd_echo_packet_input counter metallb_bfd_echo_packet_input{peer="10.46.186.88",vrf="default"} 397 # HELP metallb_bfd_echo_packet_output Number of sent BFD echo packets # TYPE metallb_bfd_echo_packet_output counter metallb_bfd_echo_packet_output{peer="10.46.186.88",vrf="default"} 397 # HELP metallb_bfd_session_down_events Number of BFD session down events # TYPE metallb_bfd_session_down_events counter metallb_bfd_session_down_events{peer="10.46.186.88",vrf="default"} 0 # HELP metallb_bfd_session_up BFD session state (1 is up, 0 is down) # TYPE metallb_bfd_session_up gauge metallb_bfd_session_up{peer="10.46.186.88",vrf="default"} 1 # HELP metallb_bfd_session_up_events Number of BFD session up events # TYPE metallb_bfd_session_up_events counter metallb_bfd_session_up_events{peer="10.46.186.88",vrf="default"} 1 # HELP metallb_bfd_zebra_notifications Number of BFD zebra notifications # TYPE metallb_bfd_zebra_notifications counter metallb_bfd_zebra_notifications{peer="10.46.186.88",vrf="default"} 2 # HELP metallb_bgp_announced_prefixes_total Number of prefixes currently being advertised on the BGP session # TYPE metallb_bgp_announced_prefixes_total gauge metallb_bgp_announced_prefixes_total{peer="10.46.186.88:179",vrf="default"} 0 # HELP metallb_bgp_keepalives_received Number of BGP keepalive messages received # TYPE metallb_bgp_keepalives_received counter metallb_bgp_keepalives_received{peer="10.46.186.88:179",vrf="default"} 2 # HELP metallb_bgp_keepalives_sent Number of BGP keepalive messages sent # TYPE metallb_bgp_keepalives_sent counter metallb_bgp_keepalives_sent{peer="10.46.186.88:179",vrf="default"} 2 # HELP metallb_bgp_notifications_sent Number of BGP notification messages sent # TYPE metallb_bgp_notifications_sent counter metallb_bgp_notifications_sent{peer="10.46.186.88:179",vrf="default"} 0 # HELP metallb_bgp_opens_received Number of BGP open messages received # TYPE metallb_bgp_opens_received counter
Additional info:
We can collect metrics via a new port, but there are no BGP or BFD metrics
oc -n metallb-system rsh -c frr-metrics frr-k8s-kmpdn curl localhost:7572/metrics | grep frr controller_runtime_active_workers{controller="frrconfiguration"} 0 controller_runtime_active_workers{controller="frrnodestate"} 0 controller_runtime_max_concurrent_reconciles{controller="frrconfiguration"} 1 controller_runtime_max_concurrent_reconciles{controller="frrnodestate"} 1 controller_runtime_reconcile_errors_total{controller="frrconfiguration"} 0 controller_runtime_reconcile_errors_total{controller="frrnodestate"} 0 controller_runtime_reconcile_time_seconds_bucket{controller="frrconfiguration",le="0.005"} 230 controller_runtime_reconcile_time_seconds_bucket{controller="frrconfiguration",le="0.01"} 230 controller_runtime_reconcile_time_seconds_bucket{controller="frrconfiguration",le="0.025"} 230 [...]
- duplicates
-
-
- Verified
-