[8101] Fix bug that confuses sonic name with alias#18744
Merged
Blueve merged 1 commit intosonic-net:masterfrom Jun 3, 2025
Merged
[8101] Fix bug that confuses sonic name with alias#18744Blueve merged 1 commit intosonic-net:masterfrom
Blueve merged 1 commit intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Blueve
approved these changes
Jun 3, 2025
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
What is the motivation for this PR? Fix 8101 fanout deployment bug How did you do it? The previous ansible template does not distinguish between sonic name and alias in the links file, which causes sonic unable to understand vlan members which should always be sonic name How did you verify/test it? Deployed fanout Any platform specific information? Cisco-8101 only Signed-off-by: opcoder0 <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
What is the motivation for this PR? Fix 8101 fanout deployment bug How did you do it? The previous ansible template does not distinguish between sonic name and alias in the links file, which causes sonic unable to understand vlan members which should always be sonic name How did you verify/test it? Deployed fanout Any platform specific information? Cisco-8101 only Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
What is the motivation for this PR? Fix 8101 fanout deployment bug How did you do it? The previous ansible template does not distinguish between sonic name and alias in the links file, which causes sonic unable to understand vlan members which should always be sonic name How did you verify/test it? Deployed fanout Any platform specific information? Cisco-8101 only Signed-off-by: Guy Shemesh <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
What is the motivation for this PR? Fix 8101 fanout deployment bug How did you do it? The previous ansible template does not distinguish between sonic name and alias in the links file, which causes sonic unable to understand vlan members which should always be sonic name How did you verify/test it? Deployed fanout Any platform specific information? Cisco-8101 only
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
What is the motivation for this PR? Fix 8101 fanout deployment bug How did you do it? The previous ansible template does not distinguish between sonic name and alias in the links file, which causes sonic unable to understand vlan members which should always be sonic name How did you verify/test it? Deployed fanout Any platform specific information? Cisco-8101 only Signed-off-by: Guy Shemesh <[email protected]>
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
…D automatically (sonic-net#18744) src/sonic-platform-daemons * dee5310 - (HEAD -> 202205, origin/202205) [ci] Fix 202205 pipeline issue. (sonic-net#474) (3 months ago) [Liu Shilong]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
The previous ansible template does not distinguish between sonic name and alias in the links file, which causes sonic unable to understand vlan members which should always be sonic name
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Fix 8101 fanout deployment bug
How did you do it?
Fix bug
How did you verify/test it?
Deployed fanout
Any platform specific information?
Cisco-8101 only
Supported testbed topology if it's a new test case?
Documentation