Fix tox errors

[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..27a9248c652c5580bb1150000adb5666d98d1924 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