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 <jbehran@cisco.com>

diff --git a/csit/libraries/NetconfKeywords.robot b/csit/libraries/NetconfKeywords.robot
index dbd3020d06988e32e96030ff5f136d4aac07df31..ec0dd0aaea314bf2996609c274e6233c83cade86 100644 (file)
--- 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