Network tests from api.network.admin.test_l3_agent_scheduler may fail in multimode environment

Bug #1817696 reported by Slawek Kaplonski
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Undecided
Slawek Kaplonski

Bug Description

API test tempest.api.network.admin.test_l3_agent_scheduler.L3AgentSchedulerTestJSON.test_add_list_remove_router_on_l3_agent may fail in some cases in multimode environment.
It will happen when neutron will be configured with l3_ha=False, so by default every created router will be nonHA router. In such case router created in mentioned test will be automatically scheduled to one of available L3 agents and then in test test_add_list_remove_router_on_l3_agent there is another attempt to add this router to some L3 agent.
If is nonHA router and it will be different agent than one on which router is already scheduled, neutron will return Conflict response.
There is no this issue for HA routers as such routers can be scheduled in more than one agent.

The solution to fix that may be to always create HA router.

Changed in tempest:
assignee: nobody → Slawek Kaplonski (slaweq)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

Fix proposed to branch: master
Review: https://review.openstack.org/639316

Changed in tempest:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tempest (master)

Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/639316
Reason: I will remove this test from tempest as same test is in neutron-tempest-plugin already. Fix for this bug will go to neutron-tempest-plugin repo

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron-tempest-plugin 0.3.0

This issue was fixed in the openstack/neutron-tempest-plugin 0.3.0 release.

Revision history for this message
Martin Kopec (mkopec) wrote :

The fix for this bug has been merged in neutron-tempest-plugin (since 0.3.0 release). I consider this bug fixed then.

Changed in tempest:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.