Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

Update test 320 to cope with persistence #2202

Merged
merged 1 commit into from
Apr 28, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions test/320_claim_3_test_disabled.sh → test/320_claim_3_test.sh
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,13 @@

. ./config.sh

delete_persistence() {
for host in "$@" ; do
docker_on $host rm -v weavedb >/dev/null
docker_on $host rm weave >/dev/null
done
}

start_suite "Claiming addresses"

weave_on $HOST1 launch-router
Expand All @@ -15,6 +22,9 @@ assert_raises "exec_on $HOST2 c2 $PING $C1"
stop_weave_on $HOST1
stop_weave_on $HOST2

# Delete persistence data so they form a blank ring
delete_persistence $HOST1 $HOST2

# Start hosts in reverse order so c1's address has to be claimed from host2
weave_on $HOST2 launch-router
weave_on $HOST1 launch-router $HOST2
Expand All @@ -31,11 +41,14 @@ assert_raises "exec_on $HOST1 c1 $PING $C3"
stop_weave_on $HOST1
stop_weave_on $HOST2

delete_persistence $HOST1 $HOST2

# Now make host1 attempt to claim from host2, when host2 is stopped
# the point being to check whether host1 will hang trying to talk to host2
weave_on $HOST2 launch-router
# Introduce host3 to remember the IPAM CRDT when we stop host2
weave_on $HOST3 launch-router $HOST2
weave_on $HOST3 prime
stop_weave_on $HOST2
weave_on $HOST1 launch-router $HOST3

Expand Down