Skip to content

Add wait_until for ARP population on linkflap testcase in test_voq_nbr.py #19344

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Javier-Tan
Copy link
Contributor

@Javier-Tan Javier-Tan commented Jul 2, 2025

Description of PR

Summary:
Fixes #19331

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

Approach

What is the motivation for this PR?

(From #19331) Fix testcase voq/test_voq_nbr.py::TestNeighborLinkFlap::test_front_panel_linkflap_port fails on condition table state delay is not reachable. This is because the test expects the ARP table to update instantly from STALE to REACHABLE after a ping is sent, which is the case for non-portchannel interfaces, however there is a small 2-3s delay state for portchannel interfaces STALE -> DELAY (2-3s) -> REACHABLE

How did you do it?

Implement a wait_until for ARP repopulation after a linkflap, similar to other testcases in the same test module

How did you verify/test it?

Ran it 5 times to ensure it's not flaky. https://elastictest.org/scheduler/testplan/6865300c3d76d955497fbe94?leftSideViewMode=detail

3x pass on minor iteration: https://elastictest.org/scheduler/testplan/686635aa6bbbe4a384a7bfd6

Any platform specific information?

N/A

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

N/A

Documentation

N/A

* Use the same wait_until that is used in other testcases in the test module for ARP repopulation

Signed-off-by: Javier Tan [email protected]
@mssonicbld
Copy link
Collaborator

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

@YatishSVC YatishSVC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, Thanks @Javier-Tan :)

…re pinged

* Move neighbor in ARP check to after all neighbors are pinged

Signed-off-by: Javier Tan [email protected]
@mssonicbld
Copy link
Collaborator

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Javier-Tan Javier-Tan requested a review from arlakshm July 3, 2025 07:44
* Fix logging typo in assert

Signed-off-by: Javier Tan [email protected]
@mssonicbld
Copy link
Collaborator

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: VoQ testcase should account for short delay for portchannel ARP to populate
7 participants