Enable secondary subnet for topo_t0-118 and fix the issue of applying secondary subnet config by ZhaohuiS · Pull Request #16864 · sonic-net/sonic-mgmt

ZhaohuiS · 2025-02-08T13:34:02Z

Description of PR

Summary:
Fixes # (issue)
#10828 enabled secondary subnet for two vlan scenarios.
But it has some issues, even add secondary_subnet: 192.169.0.1/22, there is no secondary subnet in config_db.json found.
Also fix the failures of tests/generic_config_updater/test_dynamic_acl.py and tests/acl/null_route/test_null_route_helper.py

Type of change

Back port request

Approach

What is the motivation for this PR?

Enable secondary subnet in topo_t0-118 to cover secondary subnet testing
Fix the issue of applying secondary subnet configuration.

vlan_config doesn't have secondary_subnet
ipaddr('secondary_subnet') throw error: "AnsibleFilterError: ipaddr: unknown filter type: secondary_subnet"

How did you do it?

How did you verify/test it?

After deploy-mg, secondary subnet was configured into config_db.json successfully.

admin@bjw-can-7260-11:/etc/sonic$ sudo redis-cli -n 4 keys "VLAN_INTERFACE*"
1) "VLAN_INTERFACE|Vlan1000"
2) "VLAN_INTERFACE|Vlan2000|192.168.0.129/25"
3) "VLAN_INTERFACE|Vlan1000|192.168.0.1/25"
4) "VLAN_INTERFACE|Vlan1000|192.169.0.1/22"
5) "VLAN_INTERFACE|Vlan1000|fc02:1000::1/64"
6) "VLAN_INTERFACE|Vlan2000|fc02:1000:0:1::1/64"
7) "VLAN_INTERFACE|Vlan2000"
admin@bjw-can-7260-11:/etc/sonic$ sudo zgrep "192.169" *
config_db.json:        "Vlan1000|192.169.0.1/22": {
minigraph.xml:          <SecondarySubnets>192.169.0.0/22</SecondarySubnets>
minigraph.xml:          <Prefix>192.169.0.1/22</Prefix>
admin@bjw-can-7260-11:/etc/sonic$ sudo vim minigraph.xml
admin@bjw-can-7260-11:/etc/sonic$ show ip interface
Interface       Master    IPv4 address/mask    Admin/Oper    BGP Neighbor    Neighbor IP
--------------  --------  -------------------  ------------  --------------  -------------
Loopback0                 10.1.0.32/32         up/up         N/A             N/A
PortChannel101            10.0.0.32/31         up/up         ARISTA01T1      10.0.0.33
PortChannel102            10.0.0.34/31         up/up         ARISTA02T1      10.0.0.35
PortChannel103            10.0.0.36/31         up/up         ARISTA03T1      10.0.0.37
PortChannel104            10.0.0.38/31         up/up         ARISTA04T1      10.0.0.39
Vlan1000                  192.168.0.1/25       up/up         N/A             N/A
                          192.169.0.1/22                     N/A             N/A
Vlan2000                  192.168.0.129/25     up/up         N/A             N/A
docker0                   240.127.1.1/24       up/down       N/A             N/A
eth0                      10.150.22.157/23     up/up         N/A             N/A
lo                        127.0.0.1/16         up/up         N/A             N/A

Test evidence of test_null_route_helper for 202405 with single vlan:

------------------------------------------------------------------------------------------------------------------- live log sessionfinish --------------------------------------------------------------------------------------------------------------------
08:42:15 __init__.pytest_terminal_summary         L0067 INFO   | Can not get Allure report URL. Please check logs
========================================================================================================= 1 passed, 57 warnings in 201.96s (0:03:21) ==========================================================================================================
DEBUG:tests.conftest:[log_custom_msg] item: <Function test_null_route_helper>
INFO:root:Can not get Allure report URL. Please check logs

Test evidence of test_dynamic_acl for 202411 on dualtor:

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
-------------------------------------------------------------------------------------------------- live log sessionfinish ---------------------------------------------------------------------------------------------------
11:56:28 __init__.pytest_terminal_summary         L0067 INFO   | Can not get Allure report URL. Please check logs
======================================================================================= 12 passed, 123 warnings in 2943.09s (0:49:03) =======================================================================================
DEBUG:tests.conftest:[log_custom_msg] item: <Function test_gcu_acl_nonexistent_table_removal[default-Vlan1000]>
INFO:root:Can not get Allure report URL. Please check logs

Any platform specific information?

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

Documentation

mssonicbld · 2025-02-08T13:34:05Z

/azp run

azure-pipelines · 2025-02-08T13:34:16Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2025-02-10T02:55:52Z

/azp run

azure-pipelines · 2025-02-10T02:56:04Z

Azure Pipelines successfully started running 1 pipeline(s).

ZhaohuiS · 2025-02-12T05:52:25Z

@prsunny @StormLiangMS could you please help reivew?

mssonicbld · 2025-02-17T13:39:40Z

/azp run

azure-pipelines · 2025-02-17T13:39:53Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2025-02-18T08:56:18Z

/azp run

azure-pipelines · 2025-02-18T08:56:30Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2025-02-19T08:53:13Z

/azp run

azure-pipelines · 2025-02-19T08:53:26Z

Azure Pipelines successfully started running 1 pipeline(s).

…condary subnet config Signed-off-by: Zhaohui Sun <[email protected]>

Signed-off-by: Zhaohui Sun <[email protected]>

mssonicbld · 2025-02-20T00:37:18Z

/azp run

azure-pipelines · 2025-02-20T00:37:30Z

Azure Pipelines successfully started running 1 pipeline(s).

Signed-off-by: Zhaohui Sun <[email protected]>

mssonicbld · 2025-02-20T08:46:57Z

/azp run

azure-pipelines · 2025-02-20T08:47:10Z

Azure Pipelines successfully started running 1 pipeline(s).

Signed-off-by: Zhaohui Sun <[email protected]>

mssonicbld · 2025-02-20T11:59:37Z

/azp run

ZhaohuiS · 2025-02-21T01:52:12Z

@StormLiangMS Prince Sunny's approval is stale, could you please help approve?
I also test it on 202405 and 202411

ZhaohuiS · 2025-02-21T01:53:50Z

close and reopen to trigger PR test.

mssonicbld · 2025-02-21T01:53:55Z

/azp run

azure-pipelines · 2025-02-21T01:54:07Z

Azure Pipelines successfully started running 1 pipeline(s).

StormLiangMS

LGTM

StormLiangMS · 2025-02-24T05:49:36Z

Hi @ZhaohuiS could you run test with 202405/202411 branch before cherrypick?

mssonicbld · 2025-02-24T05:51:11Z

@ZhaohuiS PR conflicts with 202405 branch

mssonicbld · 2025-02-24T05:51:11Z

@ZhaohuiS PR conflicts with 202411 branch

ZhaohuiS · 2025-02-24T05:54:09Z

Yes, already tested it. The test evidences are in the description.

… secondary subnet config (sonic-net#16864) What is the motivation for this PR? Enable secondary subnet in topo_t0-118 to cover secondary subnet testing Fix the issue of applying secondary subnet configuration. vlan_config doesn't have secondary_subnet ipaddr('secondary_subnet') throw error: "AnsibleFilterError: ipaddr: unknown filter type: secondary_subnet" How did you do it? How did you verify/test it? After deploy-mg, secondary subnet was configured into config_db.json successfully. admin@bjw-can-7260-11:/etc/sonic$ sudo redis-cli -n 4 keys "VLAN_INTERFACE*" 1) "VLAN_INTERFACE|Vlan1000" 2) "VLAN_INTERFACE|Vlan2000|192.168.0.129/25" 3) "VLAN_INTERFACE|Vlan1000|192.168.0.1/25" 4) "VLAN_INTERFACE|Vlan1000|192.169.0.1/22" 5) "VLAN_INTERFACE|Vlan1000|fc02:1000::1/64" 6) "VLAN_INTERFACE|Vlan2000|fc02:1000:0:1::1/64" 7) "VLAN_INTERFACE|Vlan2000" admin@bjw-can-7260-11:/etc/sonic$ sudo zgrep "192.169" * config_db.json: "Vlan1000|192.169.0.1/22": { minigraph.xml: <SecondarySubnets>192.169.0.0/22</SecondarySubnets> minigraph.xml: <Prefix>192.169.0.1/22</Prefix> admin@bjw-can-7260-11:/etc/sonic$ sudo vim minigraph.xml admin@bjw-can-7260-11:/etc/sonic$ show ip interface Interface Master IPv4 address/mask Admin/Oper BGP Neighbor Neighbor IP -------------- -------- ------------------- ------------ -------------- ------------- Loopback0 10.1.0.32/32 up/up N/A N/A PortChannel101 10.0.0.32/31 up/up ARISTA01T1 10.0.0.33 PortChannel102 10.0.0.34/31 up/up ARISTA02T1 10.0.0.35 PortChannel103 10.0.0.36/31 up/up ARISTA03T1 10.0.0.37 PortChannel104 10.0.0.38/31 up/up ARISTA04T1 10.0.0.39 Vlan1000 192.168.0.1/25 up/up N/A N/A 192.169.0.1/22 N/A N/A Vlan2000 192.168.0.129/25 up/up N/A N/A docker0 240.127.1.1/24 up/down N/A N/A eth0 10.150.22.157/23 up/up N/A N/A lo 127.0.0.1/16 up/up N/A N/A Test evidence of test_null_route_helper for 202405 with single vlan: ------------------------------------------------------------------------------------------------------------------- live log sessionfinish -------------------------------------------------------------------------------------------------------------------- 08:42:15 __init__.pytest_terminal_summary L0067 INFO | Can not get Allure report URL. Please check logs ========================================================================================================= 1 passed, 57 warnings in 201.96s (0:03:21) ========================================================================================================== DEBUG:tests.conftest:[log_custom_msg] item: <Function test_null_route_helper> INFO:root:Can not get Allure report URL. Please check logs Test evidence of test_dynamic_acl for 202411 on dualtor: -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html -------------------------------------------------------------------------------------------------- live log sessionfinish --------------------------------------------------------------------------------------------------- 11:56:28 __init__.pytest_terminal_summary L0067 INFO | Can not get Allure report URL. Please check logs ======================================================================================= 12 passed, 123 warnings in 2943.09s (0:49:03) ======================================================================================= DEBUG:tests.conftest:[log_custom_msg] item: <Function test_gcu_acl_nonexistent_table_removal[default-Vlan1000]> INFO:root:Can not get Allure report URL. Please check logs

… secondary subnet config (#16864) (#17118) What is the motivation for this PR? Enable secondary subnet in topo_t0-118 to cover secondary subnet testing Fix the issue of applying secondary subnet configuration. vlan_config doesn't have secondary_subnet ipaddr('secondary_subnet') throw error: "AnsibleFilterError: ipaddr: unknown filter type: secondary_subnet" How did you do it? How did you verify/test it? After deploy-mg, secondary subnet was configured into config_db.json successfully. admin@bjw-can-7260-11:/etc/sonic$ sudo redis-cli -n 4 keys "VLAN_INTERFACE*" 1) "VLAN_INTERFACE|Vlan1000" 2) "VLAN_INTERFACE|Vlan2000|192.168.0.129/25" 3) "VLAN_INTERFACE|Vlan1000|192.168.0.1/25" 4) "VLAN_INTERFACE|Vlan1000|192.169.0.1/22" 5) "VLAN_INTERFACE|Vlan1000|fc02:1000::1/64" 6) "VLAN_INTERFACE|Vlan2000|fc02:1000:0:1::1/64" 7) "VLAN_INTERFACE|Vlan2000" admin@bjw-can-7260-11:/etc/sonic$ sudo zgrep "192.169" * config_db.json: "Vlan1000|192.169.0.1/22": { minigraph.xml: <SecondarySubnets>192.169.0.0/22</SecondarySubnets> minigraph.xml: <Prefix>192.169.0.1/22</Prefix> admin@bjw-can-7260-11:/etc/sonic$ sudo vim minigraph.xml admin@bjw-can-7260-11:/etc/sonic$ show ip interface Interface Master IPv4 address/mask Admin/Oper BGP Neighbor Neighbor IP -------------- -------- ------------------- ------------ -------------- ------------- Loopback0 10.1.0.32/32 up/up N/A N/A PortChannel101 10.0.0.32/31 up/up ARISTA01T1 10.0.0.33 PortChannel102 10.0.0.34/31 up/up ARISTA02T1 10.0.0.35 PortChannel103 10.0.0.36/31 up/up ARISTA03T1 10.0.0.37 PortChannel104 10.0.0.38/31 up/up ARISTA04T1 10.0.0.39 Vlan1000 192.168.0.1/25 up/up N/A N/A 192.169.0.1/22 N/A N/A Vlan2000 192.168.0.129/25 up/up N/A N/A docker0 240.127.1.1/24 up/down N/A N/A eth0 10.150.22.157/23 up/up N/A N/A lo 127.0.0.1/16 up/up N/A N/A Test evidence of test_null_route_helper for 202405 with single vlan: ------------------------------------------------------------------------------------------------------------------- live log sessionfinish -------------------------------------------------------------------------------------------------------------------- 08:42:15 __init__.pytest_terminal_summary L0067 INFO | Can not get Allure report URL. Please check logs ========================================================================================================= 1 passed, 57 warnings in 201.96s (0:03:21) ========================================================================================================== DEBUG:tests.conftest:[log_custom_msg] item: <Function test_null_route_helper> INFO:root:Can not get Allure report URL. Please check logs Test evidence of test_dynamic_acl for 202411 on dualtor: -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html -------------------------------------------------------------------------------------------------- live log sessionfinish --------------------------------------------------------------------------------------------------- 11:56:28 __init__.pytest_terminal_summary L0067 INFO | Can not get Allure report URL. Please check logs ======================================================================================= 12 passed, 123 warnings in 2943.09s (0:49:03) ======================================================================================= DEBUG:tests.conftest:[log_custom_msg] item: <Function test_gcu_acl_nonexistent_table_removal[default-Vlan1000]> INFO:root:Can not get Allure report URL. Please check logs

… secondary subnet config (#16864) (#17119) What is the motivation for this PR? Enable secondary subnet in topo_t0-118 to cover secondary subnet testing Fix the issue of applying secondary subnet configuration. vlan_config doesn't have secondary_subnet ipaddr('secondary_subnet') throw error: "AnsibleFilterError: ipaddr: unknown filter type: secondary_subnet" How did you do it? How did you verify/test it? After deploy-mg, secondary subnet was configured into config_db.json successfully. admin@bjw-can-7260-11:/etc/sonic$ sudo redis-cli -n 4 keys "VLAN_INTERFACE*" 1) "VLAN_INTERFACE|Vlan1000" 2) "VLAN_INTERFACE|Vlan2000|192.168.0.129/25" 3) "VLAN_INTERFACE|Vlan1000|192.168.0.1/25" 4) "VLAN_INTERFACE|Vlan1000|192.169.0.1/22" 5) "VLAN_INTERFACE|Vlan1000|fc02:1000::1/64" 6) "VLAN_INTERFACE|Vlan2000|fc02:1000:0:1::1/64" 7) "VLAN_INTERFACE|Vlan2000" admin@bjw-can-7260-11:/etc/sonic$ sudo zgrep "192.169" * config_db.json: "Vlan1000|192.169.0.1/22": { minigraph.xml: <SecondarySubnets>192.169.0.0/22</SecondarySubnets> minigraph.xml: <Prefix>192.169.0.1/22</Prefix> admin@bjw-can-7260-11:/etc/sonic$ sudo vim minigraph.xml admin@bjw-can-7260-11:/etc/sonic$ show ip interface Interface Master IPv4 address/mask Admin/Oper BGP Neighbor Neighbor IP -------------- -------- ------------------- ------------ -------------- ------------- Loopback0 10.1.0.32/32 up/up N/A N/A PortChannel101 10.0.0.32/31 up/up ARISTA01T1 10.0.0.33 PortChannel102 10.0.0.34/31 up/up ARISTA02T1 10.0.0.35 PortChannel103 10.0.0.36/31 up/up ARISTA03T1 10.0.0.37 PortChannel104 10.0.0.38/31 up/up ARISTA04T1 10.0.0.39 Vlan1000 192.168.0.1/25 up/up N/A N/A 192.169.0.1/22 N/A N/A Vlan2000 192.168.0.129/25 up/up N/A N/A docker0 240.127.1.1/24 up/down N/A N/A eth0 10.150.22.157/23 up/up N/A N/A lo 127.0.0.1/16 up/up N/A N/A Test evidence of test_null_route_helper for 202405 with single vlan: ------------------------------------------------------------------------------------------------------------------- live log sessionfinish -------------------------------------------------------------------------------------------------------------------- 08:42:15 __init__.pytest_terminal_summary L0067 INFO | Can not get Allure report URL. Please check logs ========================================================================================================= 1 passed, 57 warnings in 201.96s (0:03:21) ========================================================================================================== DEBUG:tests.conftest:[log_custom_msg] item: <Function test_null_route_helper> INFO:root:Can not get Allure report URL. Please check logs Test evidence of test_dynamic_acl for 202411 on dualtor: -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html -------------------------------------------------------------------------------------------------- live log sessionfinish --------------------------------------------------------------------------------------------------- 11:56:28 __init__.pytest_terminal_summary L0067 INFO | Can not get Allure report URL. Please check logs ======================================================================================= 12 passed, 123 warnings in 2943.09s (0:49:03) ======================================================================================= DEBUG:tests.conftest:[log_custom_msg] item: <Function test_gcu_acl_nonexistent_table_removal[default-Vlan1000]> INFO:root:Can not get Allure report URL. Please check logs

vivekverma-arista · 2025-02-28T17:39:27Z

This breaks topologies with single VLAN subnet

28/02/2025 16:40:42 __init__._fixture_func_decorator         L0073 ERROR  |               
AttributeError("'AnsibleUnsafeText' object has no attribute 'get'")
Traceback (most recent call last):
  File "/data/tests/common/plugins/log_section_start/__init__.py", line 71, in _fixture_func_decorator
    return fixture_func(*args, **kargs)
  File "/data/tests/generic_config_updater/test_dynamic_acl.py", line 227, in setup  
    if config_facts['VLAN_INTERFACE'][vlan_name][vlan_ip_address].get("secondary"):
AttributeError: 'AnsibleUnsafeText' object has no attribute 'get'

… secondary subnet config (sonic-net#16864) What is the motivation for this PR? Enable secondary subnet in topo_t0-118 to cover secondary subnet testing Fix the issue of applying secondary subnet configuration. vlan_config doesn't have secondary_subnet ipaddr('secondary_subnet') throw error: "AnsibleFilterError: ipaddr: unknown filter type: secondary_subnet" How did you do it? How did you verify/test it? After deploy-mg, secondary subnet was configured into config_db.json successfully. admin@bjw-can-7260-11:/etc/sonic$ sudo redis-cli -n 4 keys "VLAN_INTERFACE*" 1) "VLAN_INTERFACE|Vlan1000" 2) "VLAN_INTERFACE|Vlan2000|192.168.0.129/25" 3) "VLAN_INTERFACE|Vlan1000|192.168.0.1/25" 4) "VLAN_INTERFACE|Vlan1000|192.169.0.1/22" 5) "VLAN_INTERFACE|Vlan1000|fc02:1000::1/64" 6) "VLAN_INTERFACE|Vlan2000|fc02:1000:0:1::1/64" 7) "VLAN_INTERFACE|Vlan2000" admin@bjw-can-7260-11:/etc/sonic$ sudo zgrep "192.169" * config_db.json: "Vlan1000|192.169.0.1/22": { minigraph.xml: <SecondarySubnets>192.169.0.0/22</SecondarySubnets> minigraph.xml: <Prefix>192.169.0.1/22</Prefix> admin@bjw-can-7260-11:/etc/sonic$ sudo vim minigraph.xml admin@bjw-can-7260-11:/etc/sonic$ show ip interface Interface Master IPv4 address/mask Admin/Oper BGP Neighbor Neighbor IP -------------- -------- ------------------- ------------ -------------- ------------- Loopback0 10.1.0.32/32 up/up N/A N/A PortChannel101 10.0.0.32/31 up/up ARISTA01T1 10.0.0.33 PortChannel102 10.0.0.34/31 up/up ARISTA02T1 10.0.0.35 PortChannel103 10.0.0.36/31 up/up ARISTA03T1 10.0.0.37 PortChannel104 10.0.0.38/31 up/up ARISTA04T1 10.0.0.39 Vlan1000 192.168.0.1/25 up/up N/A N/A 192.169.0.1/22 N/A N/A Vlan2000 192.168.0.129/25 up/up N/A N/A docker0 240.127.1.1/24 up/down N/A N/A eth0 10.150.22.157/23 up/up N/A N/A lo 127.0.0.1/16 up/up N/A N/A Test evidence of test_null_route_helper for 202405 with single vlan: ------------------------------------------------------------------------------------------------------------------- live log sessionfinish -------------------------------------------------------------------------------------------------------------------- 08:42:15 __init__.pytest_terminal_summary L0067 INFO | Can not get Allure report URL. Please check logs ========================================================================================================= 1 passed, 57 warnings in 201.96s (0:03:21) ========================================================================================================== DEBUG:tests.conftest:[log_custom_msg] item: <Function test_null_route_helper> INFO:root:Can not get Allure report URL. Please check logs Test evidence of test_dynamic_acl for 202411 on dualtor: -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html -------------------------------------------------------------------------------------------------- live log sessionfinish --------------------------------------------------------------------------------------------------- 11:56:28 __init__.pytest_terminal_summary L0067 INFO | Can not get Allure report URL. Please check logs ======================================================================================= 12 passed, 123 warnings in 2943.09s (0:49:03) ======================================================================================= DEBUG:tests.conftest:[log_custom_msg] item: <Function test_gcu_acl_nonexistent_table_removal[default-Vlan1000]> INFO:root:Can not get Allure report URL. Please check logs

ZhaohuiS requested review from StormLiangMS and prsunny February 8, 2025 13:40

ZhaohuiS force-pushed the ZhaohuiS/secondary_subnet branch from eadadf4 to a0c8bf5 Compare February 17, 2025 13:39

ZhaohuiS added Request for 202405 branch Request for 202411 branch labels Feb 18, 2025

prsunny previously approved these changes Feb 19, 2025

View reviewed changes

ZhaohuiS dismissed prsunny’s stale review via f62dea4 February 19, 2025 08:53

ZhaohuiS force-pushed the ZhaohuiS/secondary_subnet branch from d8b55de to f62dea4 Compare February 19, 2025 08:53

ZhaohuiS added 4 commits February 20, 2025 00:36

Enable secondary subnet for topo-118 and fix the issue of applying se…

6af599a

…condary subnet config Signed-off-by: Zhaohui Sun <[email protected]>

fix GCU acl failure after secondary subnet enable

2e009fc

Signed-off-by: Zhaohui Sun <[email protected]>

ignore second subnet

104af17

Signed-off-by: Zhaohui Sun <[email protected]>

fix failures in test_null_route_helper after enable secondary subnet

a0e3c36

Signed-off-by: Zhaohui Sun <[email protected]>

ZhaohuiS force-pushed the ZhaohuiS/secondary_subnet branch from f62dea4 to a0e3c36 Compare February 20, 2025 00:37

Fix failures of test_neighbor_mac_noptf

4408deb

Signed-off-by: Zhaohui Sun <[email protected]>

Add exception handling

82ab0e0

Signed-off-by: Zhaohui Sun <[email protected]>

ZhaohuiS closed this Feb 21, 2025

ZhaohuiS reopened this Feb 21, 2025

StormLiangMS approved these changes Feb 24, 2025

View reviewed changes

StormLiangMS merged commit 183d0f5 into sonic-net:master Feb 24, 2025
20 checks passed

StormLiangMS added Approved for 202405 branch Approved for 202411 branch labels Feb 24, 2025

mssonicbld added Cherry Pick Conflict_202405 Cherry Pick Conflict_202411 labels Feb 24, 2025

ZhaohuiS mentioned this pull request Feb 24, 2025

[202405] Enable secondary subnet for topo_t0-118 and fix the issue of applying secondary subnet config (#16864) #17118

Merged

11 tasks

Conversation

ZhaohuiS commented Feb 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description of PR

Type of change

Back port request

Approach

What is the motivation for this PR?

How did you do it?

How did you verify/test it?

Any platform specific information?

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

Documentation

Uh oh!

mssonicbld commented Feb 8, 2025

Uh oh!

azure-pipelines bot commented Feb 8, 2025

Uh oh!

mssonicbld commented Feb 10, 2025

Uh oh!

azure-pipelines bot commented Feb 10, 2025

Uh oh!

ZhaohuiS commented Feb 12, 2025

Uh oh!

mssonicbld commented Feb 17, 2025

Uh oh!

azure-pipelines bot commented Feb 17, 2025

Uh oh!

mssonicbld commented Feb 18, 2025

Uh oh!

azure-pipelines bot commented Feb 18, 2025

Uh oh!

mssonicbld commented Feb 19, 2025

Uh oh!

azure-pipelines bot commented Feb 19, 2025

Uh oh!

mssonicbld commented Feb 20, 2025

Uh oh!

azure-pipelines bot commented Feb 20, 2025

Uh oh!

mssonicbld commented Feb 20, 2025

Uh oh!

azure-pipelines bot commented Feb 20, 2025

Uh oh!

mssonicbld commented Feb 20, 2025

Uh oh!

ZhaohuiS commented Feb 21, 2025

Uh oh!

ZhaohuiS commented Feb 21, 2025

Uh oh!

mssonicbld commented Feb 21, 2025

Uh oh!

azure-pipelines bot commented Feb 21, 2025

Uh oh!

StormLiangMS left a comment

Choose a reason for hiding this comment

Uh oh!

StormLiangMS commented Feb 24, 2025

Uh oh!

Uh oh!

mssonicbld commented Feb 24, 2025

Uh oh!

mssonicbld commented Feb 24, 2025

Uh oh!

ZhaohuiS commented Feb 24, 2025

Uh oh!

vivekverma-arista commented Feb 28, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

ZhaohuiS commented Feb 8, 2025 •

edited

Loading