From dd9d78027b135a3413b3058449ee20a8c5d9aa60 Mon Sep 17 00:00:00 2001
From: Federico Ressi <fressi@redhat.com>
Date: Thu, 2 Sep 2021 04:38:38 +0200
Subject: [PATCH] Mark test_trunk_fip_after_reboot as flaky

The test case is often failing because of timeout issues
caused by the slow VM boot times.

Change-Id: Iad1818fa232b77f39d4fd1a4f3d7370855d709fd
---
 tobiko/tests/scenario/neutron/test_trunk.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tobiko/tests/scenario/neutron/test_trunk.py b/tobiko/tests/scenario/neutron/test_trunk.py
index 1d49b5e37..a54480f4a 100644
--- a/tobiko/tests/scenario/neutron/test_trunk.py
+++ b/tobiko/tests/scenario/neutron/test_trunk.py
@@ -33,6 +33,7 @@ class TrunkTest(testtools.TestCase):
     stack = tobiko.required_setup_fixture(
         stacks.CentosTrunkServerStackFixture)
 
+    @pytest.mark.flaky(reruns=3, reruns_delay=120)
     @pytest.mark.ovn_migration
     def test_trunk_fip_after_reboot(self):
         ping.assert_reachable_hosts([self.stack.floating_ip_address])