Disable all bmp table after test to avoid potential impact to other test cases. (sonic-net#17910)

Disable all bmp table after test to avoid potential impact to other test cases

Description of PR
Work item tracking
Microsoft ADO (number only):32206168

Approach
What is the motivation for this PR?
Disable all bmp table after test to avoid potential impact to other test cases

How did you do it?
Disable all relevant bmp table via config cli after each test.

How did you verify/test it?
kvm test verified.

Any platform specific information?

Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>

Author: FengPan-Frank

tests/bmp/test_bmp_configdb.py

@@ -89,3 +89,8 @@ def test_bmp_configdb(duthosts, rand_one_dut_hostname, localhost):
     table_name = 'bgp_rib_out_table'
     status = check_table_status(output, table_name)
     assert (status == 'true')
+
+    # disable all table to avoid further impact to other test cases
+    disable_bmp_neighbor_table(duthost)
+    disable_bmp_rib_in_table(duthost)
+    disable_bmp_rib_out_table(duthost)

tests/bmp/test_bmp_statedb.py

@@ -3,6 +3,7 @@
 import time
 import re
 from bmp.helper import enable_bmp_neighbor_table, enable_bmp_rib_in_table, enable_bmp_rib_out_table
+from bmp.helper import disable_bmp_neighbor_table, disable_bmp_rib_in_table, disable_bmp_rib_out_table
 
 logger = logging.getLogger(__name__)
 
@@ -125,3 +126,8 @@ def test_bmp_population(duthosts, rand_one_dut_hostname, localhost):
     enable_bmp_rib_out_table(duthost)
     for idx, neighbor_v6addr in enumerate(neighbor_v6addrs):
         check_dut_bmp_rib_out_status(duthost, neighbor_v6addr)
+
+    # disable all table to avoid further impact to other test cases
+    disable_bmp_neighbor_table(duthost)
+    disable_bmp_rib_in_table(duthost)
+    disable_bmp_rib_out_table(duthost)