← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1468523] Re: tempest.api.compute.test_tenant_networks should be skipped when neutron is enabled

 

No, this is not a neutron bug. External networks are visible to all
tenants.

** No longer affects: 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/1468523

Title:
  tempest.api.compute.test_tenant_networks should be skipped when
  neutron is enabled

Status in tempest:
  In Progress

Bug description:
  This test is a recipe for Neutron failures, since:

  1) it assumes there is always some tenant network
  2) it assumed it will be able do a GET on all the networks returned by the list operation

  Both #1 and #2 depend on the concurrent execution of other tests which created and destroy tenant networks.
  The test can fail because at that point in time there is no tenant network.
  Also, the test can fail because a tenant network gets deleted between the list and the show operations.

  The latter condition has begun to manifest in the gate [1]. Why only
  recently? that depends on the pattern of parallel test execution which
  depend on the number of tests and on the number of CPUs.

  Even if I'm not sure how representative is a test that lists objects from a REST endpoint and then fetches them one by one using the same endpoint, I think if it's there it must make some sense. However, when neutron is enabled it might be harmful.
  Also, neutron has a test which does pretty much the same thing in tempest.api.network. So perhaps it's not a bad idea to skip it.

  [1]
  http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRGV0YWlsczoge3UnbWVzc2FnZSc6IHUnTmV0d29yayBub3QgZm91bmQnLCB1J2NvZGUnOiA0MDR9XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjE3MjgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzUxODE1MDA3MjQsIm1vZGUiOiJzY29yZSIsImFuYWx5emVfZmllbGQiOiJidWlsZF9jaGFuZ2UifQ==

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