← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1590049] Re: test_add_list_remove_router_on_l3_agent may fail on envs where there is >= two L3 agents and DVR enabled

 

We have the same test in the neutron repo. Assaf suggested at one point
[1,2] that this is a test that should live in the neutron repo only.
Whether or not we complete the effort, we want to make sure we track
this issue in both projects.

[1] https://etherpad.openstack.org/p/neutron-tempest-defork
[2] https://bugs.launchpad.net/neutron/+bug/1552960

** Also affects: neutron
   Importance: Undecided
       Status: New

** Changed in: neutron
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1590049

Title:
  test_add_list_remove_router_on_l3_agent may fail on envs where there
  is >= two L3 agents and DVR enabled

Status in neutron:
  Confirmed
Status in tempest:
  In Progress

Bug description:
  Environment:
  OpenStack (Mitaka release), where there is more than one L3 agent and DVR enabled.

  When DVR is disabled, the resource_setup method just creates a router.
  When DVR is enabled, the resource_setup method creates a router and
  then adds an internal network interface to the created router. After
  we added the internal network interface to the router, the router is
  automatically hosted by some L3 agent. Then the test starts and tries
  to add the router to one of L3 agents and fails because the router is
  already hosted by another L3 agent.

  tempest.lib.exceptions.Conflict: An object with that identifier already exists
  Details: {u'message': u'The router 8569d347-6db4-4e12-b033-60a867ba680f has been already hosted by the L3 Agent 6250d031-d455-4afe-b993-5a7719815746.', u'type': u'RouterHostedByL3Agent', u'detail': u''}

  The full log can be found here http://paste.openstack.org/show/508686/

  A DVR router can be bound to some L3 agent without adding an internal
  network interface to the created router since the Mitaka release.

  Liberty - http://paste.openstack.org/show/574456/
  Mitaka - http://paste.openstack.org/show/574455/

  In order to fix the test, we need to remove the code block where we
  add the internal network interface to the router, but it will not work
  with the Liberty release. So we can skip the test until Liberty is EOL
  and after that fix the test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1590049/+subscriptions