yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #77405
[Bug 1819160] [NEW] Functional tests for dvr ha routers are broken
Public bug reported:
As a result of debugging issues reported in
https://bugs.launchpad.net/neutron/+bug/1818614 I found an issue with
functional tests:
test_dvr_ha_router_failover_with_gw,
test_dvr_ha_router_failover_without_gw,
test_dvr_ha_router_failover_with_gw_and_floatingip
from module neutron.tests.functional.agent.l3.test_dvr_router are
broken.
First thing which is wrong there is fact that those tests creates 2 independent routers on 2 agents. It's not one router in "master" and "standby" mode. Please check in https://github.com/openstack/neutron/blob/68fd13af40ce2752d2919ca569d3d3fe00ff6444/neutron/tests/functional/agent/l3/test_dvr_router.py#L1503
Second issue is that it assumes that always router on agent1 will be
"master" and that may be different sometimes as it depends on keepalived
negotiations.
** Affects: neutron
Importance: High
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: functional-tests gate-failure l3-dvr-backlog
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1819160
Title:
Functional tests for dvr ha routers are broken
Status in neutron:
Confirmed
Bug description:
As a result of debugging issues reported in
https://bugs.launchpad.net/neutron/+bug/1818614 I found an issue with
functional tests:
test_dvr_ha_router_failover_with_gw,
test_dvr_ha_router_failover_without_gw,
test_dvr_ha_router_failover_with_gw_and_floatingip
from module neutron.tests.functional.agent.l3.test_dvr_router are
broken.
First thing which is wrong there is fact that those tests creates 2 independent routers on 2 agents. It's not one router in "master" and "standby" mode. Please check in https://github.com/openstack/neutron/blob/68fd13af40ce2752d2919ca569d3d3fe00ff6444/neutron/tests/functional/agent/l3/test_dvr_router.py#L1503
Second issue is that it assumes that always router on agent1 will be
"master" and that may be different sometimes as it depends on
keepalived negotiations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1819160/+subscriptions
Follow ups