Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
New version of frr has come out circa two weeks ago. I am opening this bug to assess whether it is crucial for us to have this version in RHEL9 since the RHEL9-beta is getting pretty close. I would like to ask our QE for their opinion and the Openstack team, if there is a strong need to do this from their side or if we know about any customer that would need this. This is not a 'sure why not do it' kind of bug, we should have at least some arguments to do this.

As far as I am concerned, this does not seem to be a problem from the devel point of view. The initial build looks good, few minor changes in the spec file and nothing more. One problem is that we need to rebase libyang as well to the 2.0 version. This would seem like a setback but I am also maintaining libyang and frr is the only package I know of that uses this library, co I don't see a big risk here.

From the changes I can say there are a lot of bugfixes especially in the bgpd section, which might be the most important for us and our customers. There are a lot of new commands and features added but so far I did not find anything that might be incompatible with the 7.5.1 version.

Full changelog here: https://frrouting.org/release/8.0/

Thank you for updating FRR to version 8.0!

I would like to share that we also found another need for this latest version. FRR 8.9 brings new feature additions to the BFD daemon, e.g. echo receive and transmit intervals.