Code Review / integration / test.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 3a41ede) | patch
Use same tests before and after downing two nodes 82/77282/2
authorJamo Luhrsen <jluhrsen@redhat.com>
Thu, 25 Oct 2018 21:54:07 +0000 (14:54 -0700)
committerSam Hague <shague@redhat.com>
Thu, 25 Oct 2018 22:03:32 +0000 (22:03 +0000)
commitd94dfc4bb9578cb8b5bb9c97f34958544d52a1ba
tree66b4810982e2041176053ee3cbe876f0e573a518tree | snapshot
parent3a41ede028d8c54bf7c4954ec1002eca6039dd7acommit | diff
Use same tests before and after downing two nodes

Sometimes we notice a failure in connectivity after the step
to take down two of three nodes, and the node that is left
is in a bad state (maybe because it's the only node up and
cannot sync with anyone). If there is a real connectivity
issue we want to see it while a healthy cluster is running

Change-Id: Ib0251318c3b58bfdce9e8327c8a2194a4ae3dd7b
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
csit/suites/openstack/clustering/ha_l2.robot diff | blob | history
csit/suites/openstack/clustering/ha_l3.robot diff | blob | history
Integration test