Skip to content

[202512] Fix ft2 upstream neighbor map to use lt2 instead of ut2 (#24187)#1175

Open
bingwang-ms wants to merge 1 commit into
Azure:202512from
bingwang-ms:backport/24187-to-msft-202512
Open

[202512] Fix ft2 upstream neighbor map to use lt2 instead of ut2 (#24187)#1175
bingwang-ms wants to merge 1 commit into
Azure:202512from
bingwang-ms:backport/24187-to-msft-202512

Conversation

@bingwang-ms
Copy link
Copy Markdown
Contributor

Description of PR

Summary:
Cherry-pick of sonic-net/sonic-mgmt#24187 to 202512 branch.

Fix ft2 entry in UPSTREAM_ALL_NEIGHBOR_MAP from ['ut2'] to ['lt2'].

The ft2 topology connects to lt2 (leaf tier 2) upstream neighbors, not ut2. The incorrect mapping caused ntp/test_ntp.py and route/test_default_route.py to fail on ft2 testbeds because they could not find the correct upstream neighbor.

Type of change

  • Bug fix

Approach

What is the motivation for this PR?

ntp/test_ntp.py and route/test_default_route.py fail on ft2 topology testbeds because the upstream neighbor type is wrong in UPSTREAM_ALL_NEIGHBOR_MAP.

How did you do it?

Changed 'ft2': ['ut2'] to 'ft2': ['lt2'] in tests/common/helpers/constants.py.

How did you verify/test it?

Verified on testbed vms73-t0-7060x6-2 (ft2-64 topology, Arista 7060X6): ntp/test_ntp.py and route/test_default_route.py both pass (verified in original PR sonic-net/sonic-mgmt#24187).

Any platform specific information?

Specific to ft2 topology (Arista fanout, 64-port).

Documentation

N/A

…187)

Cherry-pick of PR #24187: Fix 'ft2' entry in UPSTREAM_ALL_NEIGHBOR_MAP
from ['ut2'] to ['lt2']. The ft2 topology connects to lt2 (leaf tier 2)
upstream neighbors, not ut2. The incorrect mapping caused ntp/test_ntp.py
and route/test_default_route.py to fail on ft2 testbeds.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Bing Wang <bingwang@microsoft.com>
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.

1 participant