Reference OVSDB-413 instead of bz 8529

eventually we need to move all CSIT bug references to
their JIRA counterparts, then change the bug reporting
keyword to make the link proper. For now, I just want
to stop having to figure it out when I'm vetting release
CSIT failures.

Change-Id: I4bcf1d594a29cfded0806dd18ab947bc41613553
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>

diff --git a/csit/suites/ovsdb/Southbound_Domain/020__connection_manager.robot b/csit/suites/ovsdb/Southbound_Domain/020__connection_manager.robot
index b3b41f903c8cd32d357ba1a87270eecaad0c4710..1bd996a2293ef12dd8c85d7d5b4acf39dfc397b9 100644 (file)
--- a/csit/suites/ovsdb/Southbound_Domain/020__connection_manager.robot
+++ b/csit/suites/ovsdb/Southbound_Domain/020__connection_manager.robot
@@ -124,7 +124,7 @@ Trunk And Vlan Tag Is Removed From Operational
     OVSDB.Collect OVSDB Debugs
     BuiltIn.Wait Until Keyword Succeeds    8s    2s    Utils.Check For Elements Not At URI    ${OPERATIONAL_TOPO_API}/topology/ovsdb:1    ${list}    pretty_print_json=True
     [Teardown]    Builtin.Run Keywords    Clean OVSDB Test Environment    ${TOOLS_SYSTEM_IP}
-    ...    AND    Utils.Report_Failure_Due_To_Bug    8529
+    ...    AND    Utils.Report_Failure_Due_To_Bug    OVSDB-413
 
 Check For Bug 4756
     [Documentation]    bug 4756 has been seen in the OVSDB Southbound suites. This test case should be one of the last test