RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2029958 - FRR reloader generating invalid BFD configurations, exits with error
Summary: FRR reloader generating invalid BFD configurations, exits with error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: frr
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Michal Ruprich
QA Contact: František Hrdina
URL:
Whiteboard:
Depends On:
Blocks: 2031076 2031077
TreeView+ depends on / blocked
 
Reported: 2021-12-07 16:20 UTC by Carlos Goncalves
Modified: 2022-05-10 13:58 UTC (History)
9 users (show)

Fixed In Version: frr-7.5-9.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2031076 2031077 (view as bug list)
Environment:
Last Closed: 2022-05-10 13:36:44 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-105020 0 None None None 2021-12-07 16:21:25 UTC
Red Hat Product Errata RHBA-2022:1778 0 None None None 2022-05-10 13:36:59 UTC

Description Carlos Goncalves 2021-12-07 16:20:09 UTC 
Description of problem:
The FRR reloader script is generating invalid BFD configurations and exits with an error exit code.
This issue is blocking the productization of MetalLB BFD support in OpenShift 4.10 and is an automation blocker in downstream CI.

Version-Release number of selected component (if applicable):
frr-7.5-8.el8.x86_64 (CentOS 8 Stream)

How reproducible:
100%

Steps to Reproduce:
1. install FRR
   $ sudo dnf install -y frr
2. create basic frr.conf
   $ cat /etc/frr/frr.conf
     frr version 8.1
     frr defaults traditional
     hostname centos8.localdomain
     service integrated-vtysh-config
2. $ systemctl enable --now frr
3. confirm the desired configuration is running
   # vtysh -c 'show running-config'
   Building configuration...
   
   Current configuration:
   !   
   frr version 7.5 
   frr defaults traditional
   hostname centos8.localdomain
   service integrated-vtysh-config
   !   
   line vty 
   !   
   end
4. create new-frr.conf file
   $ cat /tmp/new-frr.conf
     frr version 7.5
     frr defaults traditional
     hostname centos8.localdomain
     service integrated-vtysh-config
     !
     router bgp 64512
      bgp router-id 10.10.10.0
      no bgp ebgp-requires-policy
      no bgp default ipv4-unicast
      no bgp network import-check
      neighbor 192.168.111.1 remote-as 64512
      neighbor 192.168.111.1 bfd profile echo
      neighbor 192.168.111.1 password ibgp-test
      neighbor 192.168.111.1 timers 30 90
      !
      address-family ipv4 unicast
       neighbor 192.168.111.1 activate
      exit-address-family
      !
      address-family ipv6 unicast
       neighbor 192.168.111.1 activate
      exit-address-family
     !
     line vty
     !
     bfd
      profile echo
       transmit-interval 81
       receive-interval 80
       echo-mode
       echo-interval 82
       minimum-ttl 254
      !
     !
     end
5. invoke frr-reload
   $ /usr/lib/frr/frr-reload.py --overwrite --reload /tmp/new-frr.conf
     line 47: % Unknown command[71]:  transmit-interval 81
     line 50: % Unknown command[71]:  receive-interval 80
     line 53: % Unknown command[71]:  echo-mode
     line 56: % Unknown command[71]:  echo-interval 82
     line 59: % Unknown command[71]:  minimum-ttl 254
     line 2: % Unknown command[71]:  transmit-interval 81
     line 5: % Unknown command[71]:  receive-interval 80
     line 8: % Unknown command[71]:  echo-mode
     line 11: % Unknown command[71]:  echo-interval 82
     line 14: % Unknown command[71]:  minimum-ttl 254
     line 62: % Unknown command[71]:  transmit-interval 81
     line 65: % Unknown command[71]:  receive-interval 80
     line 68: % Unknown command[71]:  echo-mode
     line 71: % Unknown command[71]:  echo-interval 82
     line 74: % Unknown command[71]:  minimum-ttl 254


This issue has been fixed in upstream master branch [1] and backported to stable/7.5 branch [2] in January 2021.

I applied this patch to frr-7.5-8.el8.x86_64 and can confirm it fixed the issue.

    # /usr/lib/frr/frr-reload.py --overwrite --reload /tmp/new-frr.conf
    # vtysh -c 'show running-config'
    Building configuration...
    
    Current configuration:
    !
    frr version 7.5
    frr defaults traditional
    hostname centos8.localdomain
    service integrated-vtysh-config
    !
    router bgp 64512
     bgp router-id 10.10.10.0
     no bgp ebgp-requires-policy
     no bgp default ipv4-unicast
     no bgp network import-check
     neighbor 192.168.111.1 remote-as 64512
     neighbor 192.168.111.1 bfd profile echo
     neighbor 192.168.111.1 password ibgp-test
     neighbor 192.168.111.1 timers 30 90
     !
     address-family ipv4 unicast
      neighbor 192.168.111.1 activate
     exit-address-family
     !
     address-family ipv6 unicast
      neighbor 192.168.111.1 activate
     exit-address-family
    !
    line vty
    !
    bfd
     profile echo
      transmit-interval 81
      receive-interval 80
      echo-mode
      echo-interval 82
      minimum-ttl 254
     !
    !
    end


We request this commit to be backported to all impacted RHEL 8.x releases under official maintenance support.


[1] https://github.com/FRRouting/frr/pull/7891
[2] https://github.com/FRRouting/frr/commit/46a2b560fa84c5f8ece8dbb82cbf355af675ad41#diff-454217e64a66fb13ff4dfdc38ee88f97034cc88f6b42d1052898d80fce2c4f63
Comment 14 errata-xmlrpc 2022-05-10 13:36:44 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (frr bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1778
Note You need to log in before you can comment on or make changes to this bug.