Fix MDSAL nonexistent namespace error being too restrictive 92/33992/2
authorJozef Behran <jbehran@cisco.com>
Wed, 3 Feb 2016 13:18:48 +0000 (14:18 +0100)
committerJozef Behran <jbehran@cisco.com>
Thu, 4 Feb 2016 08:50:03 +0000 (09:50 +0100)
commit45433004ca2a6735647743f4dc8b20e3221d1dc9
treef219896722c04b17b0355f39f227f853eb1cdc81
parentb3aaeb2e42409e69fadf5b61d35f08f95b5c3731
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>
csit/suites/netconf/MDSAL/northbound.robot