Fix tox errors

[integration/test.git] / csit / suites / netconf / clusteringscale / topology_owner_ha.robot

diff --git a/csit/suites/netconf/clusteringscale/topology_owner_ha.robot b/csit/suites/netconf/clusteringscale/topology_owner_ha.robot
index 8c3bd1aa5f4a2064422fc172988adbdbd6187513..ddde3a9dbcc744d2dce9a5c269fbdfeed3c085e7 100644 (file)
--- a/csit/suites/netconf/clusteringscale/topology_owner_ha.robot
+++ b/csit/suites/netconf/clusteringscale/topology_owner_ha.robot
@@ -1,43 +1,43 @@
 *** Settings ***
 Documentation     Suite for High Availability testing netconf topology owner under stress.
-...           
+...
 ...               Copyright (c) 2016 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
-...           
-...           
+...
+...
 ...               Suite topology_leader_ha.robot is derived from this suite.
 ...               Please, keep the logic in the suites as similar as possible.
-...           
+...
 ...               This suite uses a Python utility to continuously configure/deconfigure
 ...               device connections against devices simulated by testtool.
 ...               The utility sends requests to the member which is leader for topology config shard.
-...           
+...
 ...               To avoid excessive resource consumption, the utility deconfigures old devices.
 ...               In a stationary state, number of config items oscillates between
 ...               ${CONFIGURED_DEVICES_LIMIT} and 1 + ${CONFIGURED_DEVICES_LIMIT}.
-...           
+...
 ...               The only tested HA event so far is reboot of the member
 ...               which is the leader of entity-ownership operational shard.
 ...               This suite assumes the entity-ownership operational shard leader and
 ...               topology config shard leader are not co-located.
-...           
+...
 ...               Number of devices is configurable, wait times are computed from that,
 ...               as it takes some time to initialize connections.
 ...               Ideally, the utility should go through half of devices during entity-ownership leader downtime.
-...           
+...
 ...               If there is a period when netconf manager ignores deletions in config datastore,
 ...               the devices created previously could "leak", meaning the number of
 ...               netconf topology items could be higher than 1 + ${CONFIGURED_DEVICES_LIMIT}.
-...           
+...
 ...               One check for correctness is the final number of devices in operational netconf topology.
 ...               Another check is performed on utility output.
-...           
+...
 ...               Performance can be estimated by the total number of requests processed,
 ...               but this suite does not perform such a computation.
-...           
+...
 ...               TODO: After stopping utility, wait to see mount has succeeded on the devices.
 Suite Setup       Setup_Everything
 Suite Teardown    Teardown_Everything