Skip to content

[vxlan] Cover VNET route survival after BGP withdrawal - #28321

Draft
zjswhhh wants to merge 2 commits into
sonic-net:masterfrom
zjswhhh:test/vnet-bgp-withdrawal-28320
Draft

zjswhhh wants to merge 2 commits into
sonic-net:masterfrom
zjswhhh:test/vnet-bgp-withdrawal-28320

Conversation

@zjswhhh

@zjswhhh zjswhhh commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Description of PR

Summary: Add a regression for VNET-first, same-prefix BGP withdrawal.

Fixes #28320. Related bug: sonic-net/sonic-swss#4910.

Type of change

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

Back port request

  • 202311
  • 202405
  • 202411
  • 202505
  • 202511
  • 202512
  • 202605

Tracking issue/work item for backport/cherry-pick request (GitHub issue or Microsoft ADO): N/A; no backport requested.
Failure type: Test coverage gap.

Tested branch

  • master
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511
  • 202512
  • 202605
  • N/A

Test result

The new test has not run on a SONiC image or testbed. Hardware validation is pending.

Approach

What is the motivation for this PR?

Existing cases do not cover activating VNET before adding and then withdrawing only BGP.

How did you do it?

Activate a custom-monitored VNET host route, add same-prefix BGP, confirm its APP_DB entry, and withdraw only BGP. Verify the original ASIC route/VR/next hop, monitor Up state, and VXLAN forwarding remain intact. Cover IPv4 /32 and IPv6 /128.

Disable VNET's local prefix advertisement only for this case so it cannot hide the competing BGP path. Reuse existing cleanup, remove synthetic monitor state, and make the neighbor helper support host prefixes.

Any platform specific information?

Inherits the suite's Cisco-8000, Mellanox, and VPP support; other platforms are skipped.

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

T1, including t1-64-lag and t1-56-lag.

Documentation

The test docstring describes the regression sequence.

Add custom-monitored IPv4 and IPv6 host-route regressions for sonic-mgmt#28320 and sonic-swss#4910. Require a competing APP_DB BGP route and preserve the VNET ASIC next hop and forwarding after withdrawal.

Signed-off-by: Jing Zhang <26625909+zjswhhh@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).

Signed-off-by: Jing Zhang <26625909+zjswhhh@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Test gap] VNET route survives same-prefix BGP withdrawal

2 participants