Skip to content

[sonic-mgmt][202505] Cast PR21616 to fix flakiness of "arp/test_stress_arp.py"#21850

Merged
StormLiangMS merged 1 commit intosonic-net:202505from
vkjammala-arista:fix-test-stress-arp-202505
Jan 8, 2026
Merged

[sonic-mgmt][202505] Cast PR21616 to fix flakiness of "arp/test_stress_arp.py"#21850
StormLiangMS merged 1 commit intosonic-net:202505from
vkjammala-arista:fix-test-stress-arp-202505

Conversation

@vkjammala-arista
Copy link
Contributor

Description of PR

Summary: Update "arp/test_stress_arp.py" test fixture to clear arp and fdb on all the duts
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
    • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Approach

How did you do it?

This is cast of #21616, see PR21616 for more details.

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

…p and fdb on all the duts

Most of testcases are sending protocol packets (arp, ipv6_echo requests
etc) from server towards ToR device. On dualtor, these protocol packets
will be processed by both the ToR duts and thus NEIGH_TABLE in APPL_DB
will be populated in both the duts (though hardware/ASIC_DB programming
will happen only on active ToR).

Fix: It's always better to clear arp and fdb tables on both the ToRs
before and after the testcase by updating "arp_cache_fdb_cleanup"
fixture to iterate over "duthosts" for cleanup.

Signed-off-by: Vinod <vkjammala@arista.com>
@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@StormLiangMS StormLiangMS merged commit 1eb5ba4 into sonic-net:202505 Jan 8, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants