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

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

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      ( ) The bug has been reproduced and verified by QE members
      ( ) Test coverage has been added to downstream CI
      ( ) For new feature, failed test plans have bugs added as children to the epic
      ( ) The bug is cloned to any relevant release that we support and/or is needed

      Show
      ( ) The bug has been reproduced and verified by QE members ( ) Test coverage has been added to downstream CI ( ) For new feature, failed test plans have bugs added as children to the epic ( ) The bug is cloned to any relevant release that we support and/or is needed
    • rhel-9
    • None

      This ticket is tracking the QE verification effort for the solution to the problem 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:
              1 Start watching this issue

                Created:
                Updated: