[Snappi] Adding Ungraceful Restart script for BGP Outbound cases #16359
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| @@ -20,8 +21,7 @@ | |||
| snappi_portchannel_ipv4_list, snappi_portchannel_ipv6_list, AS_PATHS, \ | |||
| BGP_TYPE, t1_side_interconnected_port, t2_side_interconnected_port, router_ids, \ | |||
| snappi_community_for_t1, snappi_community_for_t1_drop, snappi_community_for_t2, num_regionalhubs, \ | |||
| SNAPPI_TRIGGER, DUT_TRIGGER, fanout_presence, t2_uplink_fanout_info # noqa: F401 | |||
| from tests.common.snappi_tests.variables import v6_prefix_length | |||
| SNAPPI_TRIGGER, DUT_TRIGGER, fanout_presence, t2_uplink_fanout_info, v6_prefix_length # noqa: F401 | |||
There was a problem hiding this comment.
v6_prefix_length is no longer present in variables.py file.
| format(device_hostname, ansible_dut_hostnames)) | ||
| pytest_assert(False, "Mismatch between the dut hostnames in ansible and in variables.py files") | ||
| snappi_extra_params.device_name = t1_t2_device_hostnames[hw_platform][3] | ||
| if (len(t1_t2_device_hostnames[hw_platform]) < 3) or (len(duthosts) < 3): |
There was a problem hiding this comment.
lets remove this check for consistency.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@selldinesh PR checker(Pre_test Validate failing).. Could you fix the import error.. 2025-01-07T00:18:39.3756408Z ==================================== ERRORS ==================================== |
|
/azp run |
|
|
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Description of PR
Summary:Adding Ungraceful Restart script as part of BGP Outbound cases
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
To add Ungraceful restart case
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