yahoo-eng-team team mailing list archive

[Andrea Frittoli <1471665@xxxxxxxxxxxxxxxxxx>]

The cause for the degradation could be anywhere - keystone or any other
co-located service which is hitting your devstack node resources. The
only way Tempest could make thing worst is by not cleaning test
resources properly, which still would hardly justify the slowdown.

Such a slow down is worrying, but there's not quite enough information in the ticket to really investigate.
Could you please attach at least your local.conf and the break down of the test run times?

Initial triage is probably best done by keystone, even though the issue
could be in any of the services as they are all running on the same box.

** Project changed: tempest => keystone

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

Title:
  Successive runs of identity tempest tests take more and more time to
  finish

Status in OpenStack Identity (Keystone):
  Incomplete

Bug description:
  If I first run tempest on a newly-created VM with and install devstack
  with only keystone setup, first parallel run of
  tempest.api.identity.admin.v3 tests take around 20 seconds. If I run
  them again, they take around 38 seconds, third run would be around 48
  seconds, and so on.

  I tried on local VM (virtualbox) as well as an AWS t2.medium instance.

  Only configuration worth mentioning was:

  ENABLED_SERVICES=key,mysql,tempest

  in local.conf

  Not sure if it's only keystone specific. Nevertheless, really
  annoying.

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