Skip to content

Conversation

@markx-arista
Copy link
Contributor

Description of PR

Summary:
These topo files use same asn for VMs in each tier. This causes test_bgp_allow_list.py to fail because VMs discard routes contain their own asn.
topo_t1-isolated-v6-d56u1-lag.yml was fixed already.
Fix others by referencing to their non-v6 yml file:
e.g. topo_t1-isolated-d224u8.yml has same asn for every 8 T0 VMs.
Fixes #21574

Type of change

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

Back port request

  • 202412
  • 202505

Approach

What is the motivation for this PR?

Fix asn for v6 topo files.

How did you do it?

Fix them by referencing to their non-v6 yml file.

How did you verify/test it?

Run test_bgp_allow_list.py

Any platform specific information?

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

Documentation

These topo files use same asn for VMs in each tier.
This causes test_bgp_allow_list.py to fail because VMs
discard routes contain their own asn.
topo_t1-isolated-v6-d56u1-lag.yml was fixed already.
Fix others by referencing to their non-v6 yml file.

Signed-off-by: markxiao <[email protected]>
@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@markx-arista markx-arista reopened this Dec 8, 2025
@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: topo_t1-isolated-v6*.yml has same asn for VMs in each tier

2 participants