Fix wrong mapping type for templated requests in netconf

[integration/test.git] / csit / suites / netconf / clustering / entity-isolation-rejoin.robot

diff --git a/csit/suites/netconf/clustering/entity-isolation-rejoin.robot b/csit/suites/netconf/clustering/entity-isolation-rejoin.robot
index 04d97039b9e84183d926c272535efc9df32354ab..1133999ee556a0c7cff4ed62824efb1b4bcf9189 100644 (file)
--- a/csit/suites/netconf/clustering/entity-isolation-rejoin.robot
+++ b/csit/suites/netconf/clustering/entity-isolation-rejoin.robot
@@ -1,17 +1,17 @@
 *** Settings ***
 Documentation     Test suite for netconf device entity ownership handling during isolation.
-...           
+...
 ...               Copyright (c) 2017 Cisco Systems, Inc. and others. All rights reserved.
-...           
+...
 ...               This program and the accompanying materials are made available under the
 ...               terms of the Eclipse Public License v1.0 which accompanies this distribution,
 ...               and is available at http://www.eclipse.org/legal/epl-v10.html
-...           
-...           
+...
+...
 ...               Performs basic operations (Create, Read, Update and Delete or CRUD) on device
 ...               data mounted onto a netconf connector and verifies cluster recovery after
 ...               network isolation and rejoin of the Entity_Owner node.
-...           
+...
 ...               The suite recognizes 3 nodes,
 ...               - "CONFIGURER" (the node that configures the device at the beginning and then
 ...               deconfigures it at the end).
@@ -20,17 +20,17 @@ Documentation     Test suite for netconf device entity ownership handling during
 ...               device and the results of each data operation on it is expected to be visible
 ...               on all nodes. After each operation three test cases verify they can see the
 ...               result on their respective CONFIGURER,SETTER,CHECKER nodes.
-...           
+...
 ...               The 3 nodes are configured by placing "node1", "node2" or "node3" into the
 ...               ${NODE_CONFIGURER}, ${NODE_SETTER} and ${NODE_CHECKER} variables. This makes
 ...               a node "CONFIGURER", "SETTER" and "CHECKER" respectively.
 ...               The "nodeX" name refers to the node with its IP address configured with the
 ...               ${ODL_SYSTEM_X_IP} variable where the "X" is 1, 2 or 3.
-...           
+...
 ...               The suite verifies the presence of the device and the integrity
 ...               of device data for nodes that have at least one of the roles
 ...               ("CONFIGURER", "SETTER" and "CHECKER") assigned.
-...           
+...
 ...               TODO: Multiple improvements are possible, but apply them to entity.robot at the same time please.
 Suite Setup       Setup_Everything
 Suite Teardown    Teardown_Everything
@@ -84,7 +84,7 @@ Check_Config_Data_Before_Data_Creation
 
 Create_Device_Data
     [Documentation]    Create some data on the device and propagate it throughout the cluster.
-    ${template_as_string}=    BuiltIn.Set_Variable    {'DEVICE_NAME': '${DEVICE_NAME}'}
+    ${template_as_string}=    BuiltIn.Create_Dictionary    DEVICE_NAME=${device_name}
     TemplatedRequests.Post_As_Xml_Templated    ${directory_with_template_folders}${/}dataorig    ${template_as_string}    session=${node2_session}
 
 Check_Config_Data_After_Data_Creation
@@ -122,7 +122,7 @@ Check_Config_Data_Before_Modification_With_Original_Owner_Down
 
 Modify_Device_Data_When_Original_Owner_Is_Down
     [Documentation]    Attempt to modify the data on the device after recovery and see if it still works.
-    ${template_as_string}=    BuiltIn.Set_Variable    {'DEVICE_NAME': '${DEVICE_NAME}'}
+    ${template_as_string}=    BuiltIn.Create_Dictionary    DEVICE_NAME=${device_name}
     TemplatedRequests.Put_As_Xml_Templated    ${directory_with_template_folders}${/}datamod1    ${template_as_string}    session=${follower1_session}
 
 Check_Config_Data_After_Modification_With_Original_Owner_Down
@@ -141,7 +141,7 @@ Check_Config_Data_After_Original_Owner_Restart
 
 Modify_Device_Data_With_Original_Owner
     [Documentation]    Check that the original owner of the entity is still able to modify the data on the device
-    ${template_as_string}=    BuiltIn.Set_Variable    {'DEVICE_NAME': '${DEVICE_NAME}'}
+    ${template_as_string}=    BuiltIn.Create_Dictionary    DEVICE_NAME=${device_name}
     TemplatedRequests.Put_As_Xml_Templated    ${directory_with_template_folders}${/}datamod2    ${template_as_string}    session=${original_device_owner_session}
 
 Check_Config_Data_After_Modification_With_Original_Owner_Up