yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #07209
[Bug 1218279] Re: setUpClass (tempest.api.compute.images.test_images_oneserver.ImagesOneServerTestJSON) Failed at server creation
I actually think this was the enable/disable server race. I'm going to
close this for now. Reopen if an issue in the future
** Changed in: nova
Status: New => Fix Released
** Changed in: tempest
Status: New => Fix Released
--
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/1218279
Title:
setUpClass
(tempest.api.compute.images.test_images_oneserver.ImagesOneServerTestJSON)
Failed at server creation
Status in OpenStack Compute (Nova):
Fix Released
Status in Tempest:
Fix Released
Bug description:
http://logs.openstack.org/78/44178/1/gate/gate-tempest-devstack-vm-
postgres-full/042f00e/
2013-08-29 08:51:47.396 | FAIL: setUpClass (tempest.api.compute.images.test_images_oneserver.ImagesOneServerTestJSON)
2013-08-29 08:51:47.397 | setUpClass (tempest.api.compute.images.test_images_oneserver.ImagesOneServerTestJSON)
2013-08-29 08:51:47.397 | ----------------------------------------------------------------------
2013-08-29 08:51:47.397 | _StringException: Traceback (most recent call last):
2013-08-29 08:51:47.397 | File "tempest/api/compute/images/test_images_oneserver.py", line 50, in setUpClass
2013-08-29 08:51:47.397 | cls.tearDownClass()
2013-08-29 08:51:47.397 | File "tempest/api/compute/base.py", line 114, in tearDownClass
2013-08-29 08:51:47.398 | super(BaseComputeTest, cls).tearDownClass()
2013-08-29 08:51:47.398 | File "tempest/test.py", line 144, in tearDownClass
2013-08-29 08:51:47.398 | at_exit_set.remove(cls)
2013-08-29 08:51:47.398 | KeyError: <class 'tempest.api.compute.images.test_images_oneserver.ImagesOneServerTestJSON'>
The server creation was the actually failed.
The setUpClass attempts to call the tearDownClass on error and throws a different exception,
the correct exception throwing is tempest side issue, but the root cause probably not.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1218279/+subscriptions