Add "bug" tag so this test can be easily excluded

[integration/test.git] / csit / suites / ovsdb / Southbound_Domain / 020__connection_manager.robot

diff --git a/csit/suites/ovsdb/Southbound_Domain/020__connection_manager.robot b/csit/suites/ovsdb/Southbound_Domain/020__connection_manager.robot
index 1bd996a2293ef12dd8c85d7d5b4acf39dfc397b9..c65aaeb7aadb89f037a0b3024ea6ef30ed2a73b1 100644 (file)
--- a/csit/suites/ovsdb/Southbound_Domain/020__connection_manager.robot
+++ b/csit/suites/ovsdb/Southbound_Domain/020__connection_manager.robot
@@ -103,7 +103,7 @@ Get Operational Topology after Deletion of Bridge
 Trunk And Vlan Tag Is Removed From Operational
     [Documentation]    Verify that when the vlan tag is added and removed from an ovs port, it should be accurately reflected
     ...    in the operational store. Also verify that when all trunks are cleared from ovs, it's accurate in operational.
-    [Tags]    8529
+    [Tags]    8529    bug
     OVSDB.Clean OVSDB Test Environment    ${TOOLS_SYSTEM_IP}
     Utils.Run Command On Remote System    ${TOOLS_SYSTEM_IP}    sudo ovs-vsctl set-manager tcp:${ODL_SYSTEM_IP}:${OVSDBPORT}
     Utils.Run Command On Remote System    ${TOOLS_SYSTEM_IP}    sudo ovs-vsctl add-br vlan-tag-br