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>
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}
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
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