Comment 10 for bug 1459772

Revision history for this message
Bogdan Dobrelya (bogdando) wrote : Re: Disabling management net on a single swift node leads to a very long swift response time

How-to test:
A. how to check the swiftcheck script:
On the each swift proxy node, the command
 curl -XGET http://localhost:49001
should return OK, if the node:
- is being able to contact the management VIP by ICMP
- reports OK for the swift healthcheck via node's storate address
should return Error, if either of the checks listed above fails

B. how to check the swift proxy node control plane failover:
To get swift nodes status in HAproxy, use the command
 ip netns exec haproxy curl 'http://localhost:10000/;csv' | grep swift
executed on the node running management VIP.
- The command
 iptables -I INPUT 1 -i br-mgmt -j DROP && iptables -I OUTPUT 1 -o br-mgmt -j DROP
should mark the node down within 30 seconds.
- After that, the commands
 time swift post Container_test
 time swift upload Container_test /etc/swift/*.conf
 time swift list Container_test
 time swift delete Container_test
should report results with a reasonable delay (from seconds to few tens of seconds)
should *not* report results with a significant delay (from a minute to tens of minutes)

C. After the step B done, how to check the swift proxy node control plane failback:
- The command
 iptables -D INPUT 1 && iptables -D OUTPUT 1
should mark the node down within 30 seconds.
And ditto to the case B to the swift commands awaited results expectations.