Traceback:
ft1.10: neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_ha_router_failover_host_failuretesttools.testresult.real._StringException: Traceback (most recent call last):
File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/base.py", line 178, in func
return f(self, *args, **kwargs)
File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/fullstack/test_l3_agent.py", line 565, in test_ha_router_failover_host_failure
self._test_ha_router_failover('kill')
File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/fullstack/test_l3_agent.py", line 522, in _test_ha_router_failover
vm.assert_no_ping(external.ip)
File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/common/machine_fixtures.py", line 86, in assert_no_ping
net_helpers.assert_no_ping(self.namespace, dst_ip)
File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/common/net_helpers.py", line 168, in assert_no_ping
tools.fail("destination ip %(destination)s is replying to ping from "
File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/tools.py", line 167, in fail
raise unittest.TestCase.failureException(msg)
AssertionError: destination ip 42.0.0.15 is replying to ping from namespace test-3dc5c664-ddba-4c2e-a9a9-48bbda478506, but it shouldn't
Failure example: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_e5c/periodic/opendev.org/openstack/neutron/master/neutron-fullstack/e5cb4b0/testr_results.html
At first glance it looked like similar to https:/ /bugs.launchpad .net/neutron/ +bug/2083609 but it is not. After deeper look into this it seems for me that sometime we may hit an issue when keepalived will do failover "too fast" and vm.assert_ no_ping( external. ip) will fail as ping will be already working after keepalived will do failover.
I think we should remove that assertion from the test as it relies on the external tool (keepalived) which we can't really control and due to that we may hit issues like that from time to time.