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

CLONE [ovn25.03 fast-datapath-rhel-9] - ovn-nbctl --wait=sb returns too early

    • ovn-nbctl --wait=sb returns too early
    • 2
    • False
    • False
    • Hide

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.


      ( ) The epics work is available in a downstream build (nightly/Async or other)


      ( ) All cards under the epic have been moved to Done

      Show
      Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. ( ) The epics work is available in a downstream build (nightly/Async or other) ( ) All cards under the epic have been moved to Done
    • In Progress
    • ovn25.03-25.03.1-93.el9fdp
    • rhel-9
    • rhel-net-ovn
    • ssg_networking

      This epic tracks all the effort needed to deliver the solution related to the bug described below.
      The ovn-nbctl --wait=sb command could under certain conditions return earlier than the actual update is processed. The issue was discovered during review of https://patchwork.ozlabs.org/project/ovn/patch/20250915131602.54821-1-lucas.vdias@luizalabs.com/ the test would fail without the fix because northd entered commit fail loop. The expected behavior would be for the sync call to block until the timeout runs out. However the sync call was returning 0 and the test failed later on database check.

       

      The root cause is that northd I-P wouldn't run, but there was still valid transaction for SB. The transaction commit would return UNCHANGED, however, UNCHANGED moves idl loop next_cfg to cur_cfg, which is used by the synchronization. The next northd loop would update the SB nb_cfg in a different transaction than the failing one. Resulting in sync returning early.

              ovn-qe OVN QE
              ovnteam@redhat.com OVN Team
              OVN QE OVN QE
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: