• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • ovn23.09
    • 13
    • False
    • False
    • Hide

      Given the system administrator has multiple OCP clusters deployed on top of OSP and these clusters are undergoing a failover scenario or experiencing high GARP traffic, 

      When ovn-northd receives high-frequency gARPs from multiple sources during a failover or similar event, 

      Then, ovn-northd should be able to process this traffic without overloading, maintaining stable CPU usage and avoiding cluster-wide failover effects.

      Show
      Given the system administrator has multiple OCP clusters deployed on top of OSP and these clusters are undergoing a failover scenario or experiencing high GARP traffic,  When ovn-northd receives high-frequency gARPs from multiple sources during a failover or similar event,  Then, ovn-northd should be able to process this traffic without overloading, maintaining stable CPU usage and avoiding cluster-wide failover effects.
    • rhel-sst-network-fastdatapath-ovn
    • ssg_networking
    • FDP 24.E, FDP 24.F, FDP 24.G, OVN FDP 25.C
    • 4

      We had a customer case where lots of OCP clusters are deployed on top of OpenStack. An OSP upgrade attempt triggered OCP VIP failover that loaded ovn-northd so much that other OCP clusters started their failovers too causing a snowball effect.

      The dataplane has never recovered fully and OCPs kept sending gratuitous ARPs periodically from all their nodes, causing lot of virtual parent ports updates in the southbound DB.

      This ticket serves as a discussion starter how to make OVN more resilient to gARPs coming from multiple sources at the same time.

              amusil@redhat.com Ales Musil
              jlibosva Jakub Libosvar
              Jianlin Shi Jianlin Shi
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: