← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1338841] Re: EC2KeysTest fails in tearDownClass with InvalidKeyPair.Duplicate

 

Multiple trove workers also merged on 7/8:

https://review.openstack.org/#/c/103239/

And glance api/registry workers to use number of CPUs by default merged
on 7/3:

https://review.openstack.org/102665

So maybe the cinder api workers change just tipped it over.

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

** Summary changed:

- EC2KeysTest fails in tearDownClass with InvalidKeyPair.Duplicate
+ asynchronous connection failed in postgresql jobs

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1338841

Title:
  asynchronous connection failed in postgresql jobs

Status in Cinder:
  New
Status in OpenStack Compute (Nova):
  New

Bug description:
  The trace for the failure is here:

  http://logs.openstack.org/57/105257/4/check/check-tempest-dsvm-
  postgres-
  full/f72b818/logs/tempest.txt.gz?level=TRACE#_2014-07-07_23_43_37_250

  This is the console error:

  2014-07-07 23:44:59.590 | tearDownClass (tempest.thirdparty.boto.test_ec2_keys.EC2KeysTest)
  2014-07-07 23:44:59.590 | -----------------------------------------------------------------
  2014-07-07 23:44:59.590 | 
  2014-07-07 23:44:59.590 | Captured traceback:
  2014-07-07 23:44:59.590 | ~~~~~~~~~~~~~~~~~~~
  2014-07-07 23:44:59.590 |     Traceback (most recent call last):
  2014-07-07 23:44:59.590 |       File "tempest/thirdparty/boto/test.py", line 272, in tearDownClass
  2014-07-07 23:44:59.590 |         raise exceptions.TearDownException(num=fail_count)
  2014-07-07 23:44:59.590 |     TearDownException: 1 cleanUp operation failed

  There isn't much in the n-api logs, just the 400 response.

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


References