yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

Public bug reported:

I've written a tempest test which creates 2 servers in nova which don't
have any networking available in the tenant when the server create
request is made. This invokes the auto_allocated_topology API in neutron
to create the networking resources for the tenant.

The test failed because it expects at the end that there is only one
private network for the tenant created but in this case there were two:

http://logs.openstack.org/01/327901/1/check/gate-tempest-dsvm-neutron-
full/9972b81/console.html#_2016-06-12_15_19_25_240

Showing that the network create wasn't atomic per tenant in concurrent
requests from nova's compute manager.

** Affects: neutron
     Importance: High
         Status: Confirmed


** Tags: auto-allocated-topology

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

Title:
  auto_allocated_topology network creation isn't atomic per tenant

Status in neutron:
  Confirmed

Bug description:
  I've written a tempest test which creates 2 servers in nova which
  don't have any networking available in the tenant when the server
  create request is made. This invokes the auto_allocated_topology API
  in neutron to create the networking resources for the tenant.

  The test failed because it expects at the end that there is only one
  private network for the tenant created but in this case there were
  two:

  http://logs.openstack.org/01/327901/1/check/gate-tempest-dsvm-neutron-
  full/9972b81/console.html#_2016-06-12_15_19_25_240

  Showing that the network create wasn't atomic per tenant in concurrent
  requests from nova's compute manager.

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