selftests: mptcp: connect: fail if nft supposed to work
authorMatthieu Baerts <matthieu.baerts@tessares.net>
Tue, 4 Jul 2023 20:44:35 +0000 (22:44 +0200)
committerDavid S. Miller <davem@davemloft.net>
Wed, 5 Jul 2023 09:51:14 +0000 (10:51 +0100)
In case of "external" errors when preparing the environment for the
TProxy tests, the subtests were marked as skipped.

This is fine but it means these errors are ignored. On MPTCP Public CI,
we do want to catch such issues and mark the selftest as failed if there
are such issues. We can then use mptcp_lib_fail_if_expected_feature()
helper that has been recently added to fail if needed.

Link: https://github.com/multipath-tcp/mptcp_net-next/issues/368
Fixes: 5fb62e9cd3ad ("selftests: mptcp: add tproxy test case")
Cc: stable@vger.kernel.org
Acked-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
tools/testing/selftests/net/mptcp/mptcp_connect.sh

index 13561e5..bbae408 100755 (executable)
@@ -718,6 +718,7 @@ table inet mangle {
 EOF
        if [ $? -ne 0 ]; then
                echo "SKIP: $msg, could not load nft ruleset"
+               mptcp_lib_fail_if_expected_feature "nft rules"
                return
        fi
 
@@ -733,6 +734,7 @@ EOF
        if [ $? -ne 0 ]; then
                ip netns exec "$listener_ns" nft flush ruleset
                echo "SKIP: $msg, ip $r6flag rule failed"
+               mptcp_lib_fail_if_expected_feature "ip rule"
                return
        fi
 
@@ -741,6 +743,7 @@ EOF
                ip netns exec "$listener_ns" nft flush ruleset
                ip -net "$listener_ns" $r6flag rule del fwmark 1 lookup 100
                echo "SKIP: $msg, ip route add local $local_addr failed"
+               mptcp_lib_fail_if_expected_feature "ip route"
                return
        fi