Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-125957

add frr10 package [rhel-9.8]

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • rhel-net-perf
    • 0
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • _N&P-Refined_
    • Enhancement
    • Hide
      Renoa first draft:
       Due to the absence of the Downstream VNI/Single Vxlan device feature in FRR for RHEL9 on OpenShift Platform, users may encounter USB4 activation issues on Dell WD25/SD25 devices, affecting data transfer functionality. To rectify this, it's recommended to implement FRR10, a new package incorporating code from pull requests 8647 and 12364, which addresses the missing feature. As a result, users can expect improved performance on OpenShift Platform with the latest FRR in RHEL9, delivered through the addition of the Downstream VNI/Single Vxlan device feature via the new versioned package - FRR10.
      Show
      Renoa first draft:  Due to the absence of the Downstream VNI/Single Vxlan device feature in FRR for RHEL9 on OpenShift Platform, users may encounter USB4 activation issues on Dell WD25/SD25 devices, affecting data transfer functionality. To rectify this, it's recommended to implement FRR10, a new package incorporating code from pull requests 8647 and 12364, which addresses the missing feature. As a result, users can expect improved performance on OpenShift Platform with the latest FRR in RHEL9, delivered through the addition of the Downstream VNI/Single Vxlan device feature via the new versioned package - FRR10.
    • Proposed
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      There is a need in of the latest FRR in RHEL9 that is coming from OpenShift Platform. The feature that is needed from FRR is called "Downstream VNI/Single Vxlan device". Some of the code that needs to be present in our version of FRR includes the following:
      https://github.com/FRRouting/frr/pull/8647
      https://github.com/FRRouting/frr/pull/12364

      A couple of options have been discussed including shipping FRR in FDP or rebasing the package. The rebase of the package this late in RHEL9 release cycle is risky but so is the backporting of so many changes in the current version. One option would be to deliver a versioned FRR that would be added as a new package - FRR10. This issue is meant for tracking of tasks and for any investigative steps that are needed to deliver this feature.

        1. frr10.spec
          16 kB

              mruprich@redhat.com Michal Ruprich
              mruprich@redhat.com Michal Ruprich
              Michal Ruprich Michal Ruprich
              Frantisek Hrdina Frantisek Hrdina
              Lucie Varakova Lucie Varakova
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: