[dualtor][test_bgp_session] Skip reboot test type on dualtor

[lolyu]

Description of PR

Summary: Fixes # (issue)

Type of change

• [x] Bug fix
• [ ] Testbed and Framework(new/improvement)
• [ ] Test case(new/improvement)

Back port request

• [ ] 202012
• [ ] 202205
• [ ] 202305
• [ ] 202311
• [x] 202405

Approach

What is the motivation for this PR?

Skip the warm reboot test type, as it will leave the DUT in an error state, and causes failures of following cases:

bgp/test_bgp_session.py::test_bgp_session_interface_down[interface-bgp_docker] PASSED [ 16%]
bgp/test_bgp_session.py::test_bgp_session_interface_down[interface-swss_docker] PASSED [ 33%]
bgp/test_bgp_session.py::test_bgp_session_interface_down[interface-reboot] FAILED [ 50%]
bgp/test_bgp_session.py::test_bgp_session_interface_down[neighbor-bgp_docker] FAILED [ 66%]
bgp/test_bgp_session.py::test_bgp_session_interface_down[neighbor-swss_docker] FAILED [ 83%]
bgp/test_bgp_session.py::test_bgp_session_interface_down[neighbor-reboot] FAILED [100%]

Signed-off-by: Longxiang Lyu lolv@microsoft.com

How did you do it?

If test type is reboot (warm reboot), skip on dualtor.

How did you verify/test it?

bgp/test_bgp_session.py::test_bgp_session_interface_down[neighbor-reboot] SKIPPED (warm reboot is not supported on dualtor)                                                                                                                                            [100%]
bgp/test_bgp_session.py::test_bgp_session_interface_down[neighbor-bgp_docker] PASSED                                                                                                                                                                                   [100%]

Any platform specific information?

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

Documentation