yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

e-r query here: https://review.openstack.org/#/c/114359/

If this is mostly just neutron full jobs, this might make sense, i.e.
those run with tenant isolation so maybe there are multiple tests
running at the same time allocating ports on the same subnet and then
when one test completes and tries to tear down it wants to delete the
subnet which is still got one or more ports on it, so we fail.

Seems like we could just do a simple check in the nova neutronv2 API
before trying to delete the subnet to see if there are any ports still
assigned, or just handle the 409 and move on.

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

** Tags added: network neutron

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

Title:
  Race to delete shared subnet in Tempest neutron full jobs

Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Compute (Nova):
  New

Bug description:
  This seems to show up in several different tests, basically anything
  using neutron.  I noticed it here:

  http://logs.openstack.org/89/112889/1/gate/check-tempest-dsvm-neutron-
  full/21fcf50/console.html#_2014-08-14_17_03_10_330

  That's on a stable/icehouse change, but logstash shows this on master
  mostly.

  I see this in the neutron server logs:

  http://logs.openstack.org/89/112889/1/gate/check-tempest-dsvm-neutron-
  full/21fcf50/logs/screen-q-svc.txt.gz#_2014-08-14_16_45_02_101

  This query shows 82 hits in 10 days:

  message:"delete failed \(client error\)\: Unable to complete operation
  on subnet" AND message:"One or more ports have an IP allocation from
  this subnet" AND tags:"screen-q-svc.txt"

  http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiZGVsZXRlIGZhaWxlZCBcXChjbGllbnQgZXJyb3JcXClcXDogVW5hYmxlIHRvIGNvbXBsZXRlIG9wZXJhdGlvbiBvbiBzdWJuZXRcIiBBTkQgbWVzc2FnZTpcIk9uZSBvciBtb3JlIHBvcnRzIGhhdmUgYW4gSVAgYWxsb2NhdGlvbiBmcm9tIHRoaXMgc3VibmV0XCIgQU5EIHRhZ3M6XCJzY3JlZW4tcS1zdmMudHh0XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wNy0zMVQxOTo0Mzo0NSswMDowMCIsInRvIjoiMjAxNC0wOC0xNFQxOTo0Mzo0NSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxNDA4MDQ1NDY1OTU2fQ==

  Logstash doesn't show this in the gate queue but it does show up in
  the uncategorized bugs list which is in the gate queue.

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