Fix MDSAL nonexistent namespace error being too restrictive

All that is needed is that the response contains a
<rpc-error> tag and that it mentions the bogus namespace.
Insisting on having also "does-not-exist" or other texts in
the error message is superfluous and easily leads to
spurious failures.

Change-Id: I202f4bf2a81573106763136a0d9bf4cc1bb5d8a2
Signed-off-by: Jozef Behran <jbehran@cisco.com>

diff --git a/csit/suites/netconf/MDSAL/northbound.robot b/csit/suites/netconf/MDSAL/northbound.robot
index 80e26b6e9ab0432ca5f8da667d9d157658cd9cb8..f635b6e9c4201d890be545c6b2e2e9b28b39037a 100644 (file)
--- a/csit/suites/netconf/MDSAL/northbound.robot
+++ b/csit/suites/netconf/MDSAL/northbound.robot
@@ -73,7 +73,7 @@ Send_Stuff_In_Undefined_Namespace
     BuiltIn.Should_Not_Contain    ${reply}    java.lang.NullPointerException
     BuiltIn.Set_Test_Variable    ${bugno}    ${EMPTY}
     BuiltIn.Should_Contain    ${reply}    urn:this:is:in:a:nonexistent:namespace
-    BuiltIn.Should_Contain    ${reply}    does-not-exist
+    BuiltIn.Should_Contain    ${reply}    <rpc-error>
     [Teardown]    BuiltIn.Run_Keyword_If    '${bugno}' != '${EMPTY}'    Utils.Report_Failure_Due_To_Bug    5125
 
 Edit_Config_First_Batch_Merge