From 23e0107f677e01577f9166f4d6bb7812d72a73dc Mon Sep 17 00:00:00 2001 From: Jozef Behran Date: Fri, 20 Nov 2015 15:10:33 +0100 Subject: [PATCH] Fix Wait_Device_Fully_Removed querying the wrong URL When the device data is gone (device was disconnectd) but the connector itself is still there, the keyword thinks the device is no longer there and exits but the device is still there and might stay due to a bug. Fix this by shortening the URL to refer to the root of the connector, that should catch such bugs. Change-Id: Iddf55b3e5842e50828a327f4b442d0a6bd126e7f Signed-off-by: Jozef Behran --- csit/libraries/NetconfKeywords.robot | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/csit/libraries/NetconfKeywords.robot b/csit/libraries/NetconfKeywords.robot index dbd3020d06..ec0dd0aaea 100644 --- a/csit/libraries/NetconfKeywords.robot +++ b/csit/libraries/NetconfKeywords.robot @@ -52,7 +52,7 @@ Check_Device_Completely_Gone [Arguments] ${device_name} [Documentation] Check that the specified device has no Netconf connectors nor associated data. Check_Device_Has_No_Netconf_Connector ${device_name} - ${uri}= Builtin.Set_Variable network-topology:network-topology/topology/topology-netconf/node/${device_name}/yang-ext:mount + ${uri}= Builtin.Set_Variable network-topology:network-topology/topology/topology-netconf/node/${device_name} ${response}= RequestsLibrary.Get Request nvr_session ${uri} ${ACCEPT_XML} BuiltIn.Should_Be_Equal_As_Integers ${response.status_code} 404 -- 2.36.6