Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-2854

Upstream: ovs-vswitchd becomes completely unresponsive when setting enable-chassis-as-gw on EDPM node

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • openvswitch3.5
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:
      ( ) Unit test or Integration test case are written and pass successfully


      ( ) The upstream pull request is merged upstream and pass CI

      Show
      Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) Unit test or Integration test case are written and pass successfully ( ) The upstream pull request is merged upstream and pass CI
    • rhel-9
    • None
    • rhel-net-ovn

      This is tracking the upstream effort needed to deliver the solution to the bug described below.


      On a EDPM / Compute node, once we do ovs-vsctl set open . external_ids:ovn-cms-options=enable-chassis-as-gw any ovs comand enters deadlock and never returns.
       
      Any ovs commands is stalling and never returns (like ovs-appctl ofproto/list, ovs-vsctl add-br testbr just stuck)

       
      openvswitch3.5-3.5.0-19.el9fdp.x86_64
      ovn24.03-host-24.03.5-98.el9fdp.x86_64

       Every time we set the node as gateway chassis this happens on any of the 3 computes nodes currently deployed.


              ovsdpdk-triage ovsdpdk triage
              nstbot NST Bot
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: