commit e07c36d8f4a0e1b938571ab7540a8a39965c8b7b
Author: Michele Baldessari <michele@acksyn.org>
Date:   Wed Oct 7 17:34:49 2020 +0200

    When creating a network disruption we should use DROP
    
    Currently in a network disruption we use REJECT with
    icmp-host-prohibited. This seems to be too niche. A usual network
    disruption will just not forward any packets full stop
    so DROP sounds a bit more correct (think of a faulty switch for example)
    
    Change-Id: Ie7b149dc71d098f744849ae2f9f99895e5e36225

diff --git a/tobiko/tests/faults/ha/cloud_disruptions.py b/tobiko/tests/faults/ha/cloud_disruptions.py
index 90d4f04..40b890a 100644
--- a/tobiko/tests/faults/ha/cloud_disruptions.py
+++ b/tobiko/tests/faults/ha/cloud_disruptions.py
@@ -31,9 +31,9 @@ network_disruption = """
  sudo iptables -I INPUT 1 -m state --state RELATED,ESTABLISHED -j ACCEPT &&
  sudo iptables -I INPUT 2 -p tcp -m state --state NEW -m tcp --dport 22 -j \
  ACCEPT &&
- sudo iptables -I INPUT 3 ! -i lo -j REJECT --reject-with icmp-host-prohibited\
-  && sudo iptables -I OUTPUT 1 -p tcp --sport 22 -j ACCEPT &&
- sudo iptables -I OUTPUT 2 ! -o lo -j REJECT --reject-with icmp-host-prohibited
+ sudo iptables -I INPUT 3 ! -i lo -j DROP &&
+ sudo iptables -I OUTPUT 1 -p tcp --sport 22 -j ACCEPT &&
+ sudo iptables -I OUTPUT 2 ! -o lo -j DROP
 """
 
 undisrupt_network = """