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

QE verification: ovn-nbctl --wait=sb returns too early

    • 1
    • False
    • 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
    • ovn24.03-24.03.6-45.el9fdp
    • rhel-9
    • None
    • -

      This ticket is tracking the QE verification effort for the solution to the problem 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.

              ovnteam@redhat.com OVN Team
              nstbot NST Bot
              Ehsan Elahi Ehsan Elahi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: