Issue 20728: Enhance configlet/test_add_rack.py for ipv6-only topos#21591
Merged
yanmo96 merged 2 commits intosonic-net:masterfrom Mar 13, 2026
Merged
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
901068c to
71be742
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
71be742 to
ede382f
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ede382f to
aa1938f
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azpw |
aa1938f to
fbf5115
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
@yanmo96 Can you help review this PR? Thanks |
fbf5115 to
c23e5ca
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azpw run |
Collaborator
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azpw run |
Collaborator
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
@yxieca here's another one that's passing all the checks |
Contributor
|
Hi @anders-nexthop trying to merge, but some conflicts need to be resolve |
Currently, the test checks for both ipv4 and ipv6 neighbors unconditionally, and will fail if either is missing. Change that behavior to instead check to see if neighbors exist before running the bgp checks. Add a failure case if no neighbors are found in either AF. This way the test is AF-agnostic. Signed-off-by: Anders Linn <[email protected]>
Signed-off-by: Anders Linn <[email protected]>
ac5e4bd to
40c4d72
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
Thanks @yanmo96 yes some conflicts just came in, i have resolved them and updated the PR. |
Contributor
Author
|
@yanmo96 all checks are passing now |
selldinesh
pushed a commit
to selldinesh/sonic-mgmt
that referenced
this pull request
Mar 16, 2026
…onic-net#21591) * Issue 20728: Enhance configlet/test_add_rack.py for ipv6-only topos Currently, the test checks for both ipv4 and ipv6 neighbors unconditionally, and will fail if either is missing. Change that behavior to instead check to see if neighbors exist before running the bgp checks. Add a failure case if no neighbors are found in either AF. This way the test is AF-agnostic. Signed-off-by: Anders Linn <[email protected]> * Address review comments Signed-off-by: Anders Linn <[email protected]> --------- Signed-off-by: Anders Linn <[email protected]> Signed-off-by: selldinesh <[email protected]>
abhishek-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Mar 17, 2026
…onic-net#21591) * Issue 20728: Enhance configlet/test_add_rack.py for ipv6-only topos Currently, the test checks for both ipv4 and ipv6 neighbors unconditionally, and will fail if either is missing. Change that behavior to instead check to see if neighbors exist before running the bgp checks. Add a failure case if no neighbors are found in either AF. This way the test is AF-agnostic. Signed-off-by: Anders Linn <[email protected]> * Address review comments Signed-off-by: Anders Linn <[email protected]> --------- Signed-off-by: Anders Linn <[email protected]> Signed-off-by: Abhishek <[email protected]>
Contributor
|
Hi @anders-nexthop , 202511 branch also need this fix, could you help cherry-pick? thanks |
vrajeshe
pushed a commit
to vrajeshe/sonic-mgmt
that referenced
this pull request
Mar 23, 2026
…onic-net#21591) * Issue 20728: Enhance configlet/test_add_rack.py for ipv6-only topos Currently, the test checks for both ipv4 and ipv6 neighbors unconditionally, and will fail if either is missing. Change that behavior to instead check to see if neighbors exist before running the bgp checks. Add a failure case if no neighbors are found in either AF. This way the test is AF-agnostic. Signed-off-by: Anders Linn <[email protected]> * Address review comments Signed-off-by: Anders Linn <[email protected]> --------- Signed-off-by: Anders Linn <[email protected]> Signed-off-by: Venkata Gouri Rajesh Etla <[email protected]>
weiguo-nvidia
added a commit
to weiguo-nvidia/sonic-mgmt
that referenced
this pull request
Mar 24, 2026
PR sonic-net#22895 added BGP session convergence wait before DB comparison in generic_patch_add_t0(), but unconditionally checks both IPv4 and IPv6 BGP sessions. On IPv6-only topologies (e.g. t1-isolated-v6-d56u1-lag), tor_data["ip"]["remote"] is empty, causing is_bgp_session_established() to fail. Fix by checking whether each neighbor IP exists before waiting for the BGP session, consistent with the chk_any_bgp_session() approach from PR sonic-net#21591. Change-Id: I694fd17b7b49b4ce4ece53e0521773b71f301b70 Signed-off-by: weiguo-nvidia <[email protected]>
12 tasks
anders-nexthop
added a commit
to anders-nexthop/sonic-mgmt
that referenced
this pull request
Mar 25, 2026
…onic-net#21591) * Issue 20728: Enhance configlet/test_add_rack.py for ipv6-only topos Currently, the test checks for both ipv4 and ipv6 neighbors unconditionally, and will fail if either is missing. Change that behavior to instead check to see if neighbors exist before running the bgp checks. Add a failure case if no neighbors are found in either AF. This way the test is AF-agnostic. Signed-off-by: Anders Linn <[email protected]> * Address review comments Signed-off-by: Anders Linn <[email protected]> --------- Signed-off-by: Anders Linn <[email protected]>
Merged
12 tasks
Contributor
Author
|
Hi @weiguo-nvidia, cherry-pick to 202511 is up at #23321. — anders-bot (AI-assisted, on behalf of @anders-nexthop) |
yxieca
pushed a commit
that referenced
this pull request
Mar 26, 2026
…#23241) What is the motivation for this PR?\nPR #22895 added BGP session convergence wait before DB comparison in generic_patch_add_t0(), but unconditionally checks both IPv4 and IPv6 BGP sessions. On IPv6-only topologies (e.g. t1-isolated-v6-d56u1-lag), tor_data["ip"]["remote"] is empty, causing is_bgp_session_established() to fail.\n\nHow did you do it?\nFix by checking whether each neighbor IP exists before waiting for the BGP session, consistent with the chk_any_bgp_session() approach from PR #21591.\n\nHow did you verify/test it?\nRegression test pass\n\nSigned-off-by:\nweiguo-nvidia <[email protected]>
ravaliyel
pushed a commit
to ravaliyel/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
…onic-net#21591) * Issue 20728: Enhance configlet/test_add_rack.py for ipv6-only topos Currently, the test checks for both ipv4 and ipv6 neighbors unconditionally, and will fail if either is missing. Change that behavior to instead check to see if neighbors exist before running the bgp checks. Add a failure case if no neighbors are found in either AF. This way the test is AF-agnostic. Signed-off-by: Anders Linn <[email protected]> * Address review comments Signed-off-by: Anders Linn <[email protected]> --------- Signed-off-by: Anders Linn <[email protected]>
ravaliyel
pushed a commit
to ravaliyel/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
…sonic-net#23241) What is the motivation for this PR?\nPR sonic-net#22895 added BGP session convergence wait before DB comparison in generic_patch_add_t0(), but unconditionally checks both IPv4 and IPv6 BGP sessions. On IPv6-only topologies (e.g. t1-isolated-v6-d56u1-lag), tor_data["ip"]["remote"] is empty, causing is_bgp_session_established() to fail.\n\nHow did you do it?\nFix by checking whether each neighbor IP exists before waiting for the BGP session, consistent with the chk_any_bgp_session() approach from PR sonic-net#21591.\n\nHow did you verify/test it?\nRegression test pass\n\nSigned-off-by:\nweiguo-nvidia <[email protected]>
vmittal-msft
pushed a commit
that referenced
this pull request
Mar 27, 2026
…21591) (#23321) * Issue 20728: Enhance configlet/test_add_rack.py for ipv6-only topos Currently, the test checks for both ipv4 and ipv6 neighbors unconditionally, and will fail if either is missing. Change that behavior to instead check to see if neighbors exist before running the bgp checks. Add a failure case if no neighbors are found in either AF. This way the test is AF-agnostic. * Address review comments --------- Signed-off-by: Anders Linn <[email protected]>
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
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
Summary:
Currently, the test checks for both ipv4 and ipv6 neighbors unconditionally, and will fail if either is missing. Change that behavior to instead check to see if neighbors exist before running the bgp checks. Add a failure case if no neighbors are found in either AF. This way the test is AF-agnostic.
Closes #20728
Type of change
Back port request
Approach
What is the motivation for this PR?
Extend coverage for IPv6-only topos
How did you do it?
Add logic to check whether v4/v6 neighbor ips exist before checking whether they are up. If no neighbor ips are found at all, the test fails.
How did you verify/test it?
Ran the test on a vs topo with only v6 neighbors. It fails before these changes and passes after they are added.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation