yahoo-eng-team team mailing list archive

Thread
Date
[Bug 1347692] [NEW] gate failure with tempest.api.image.v1.test_images.CreateRegisterImagesTest.test_register_http_image

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Chris Dent <chdent@xxxxxxxxxx>
Date: Wed, 23 Jul 2014 13:28:05 -0000
Reply-to: Bug 1347692 <1347692@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Public bug reported:

In review https://review.openstack.org/#/c/108410/ I get a failure with
check-tempest-dsvm-postgres-full.

(note this is not a duplicate of
https://bugs.launchpad.net/glance/+bug/1247194 )

Presumably this is a timeout, or something getting ahead of something
else. Reporting to be a good boy.

Logs and links to logs below:

2014-07-23 11:02:18.128 | ==============================
2014-07-23 11:02:18.128 | Failed 1 tests - output below:
2014-07-23 11:02:18.128 | ==============================
2014-07-23 11:02:18.128 | 
2014-07-23 11:02:18.128 | tempest.api.image.v1.test_images.CreateRegisterImagesTest.test_register_http_image[gate]
2014-07-23 11:02:18.128 | ----------------------------------------------------------------------------------------
2014-07-23 11:02:18.128 | 
2014-07-23 11:02:18.128 | Captured traceback:
2014-07-23 11:02:18.128 | ~~~~~~~~~~~~~~~~~~~
2014-07-23 11:02:18.128 |     Traceback (most recent call last):
2014-07-23 11:02:18.128 |       File "tempest/api/image/v1/test_images.py", line 79, in test_register_http_image
2014-07-23 11:02:18.128 |         self.client.wait_for_image_status(image_id, 'active')
2014-07-23 11:02:18.129 |       File "tempest/services/image/v1/json/image_client.py", line 295, in wait_for_image_status
2014-07-23 11:02:18.129 |         status=status)
2014-07-23 11:02:18.129 |     ImageKilledException: Image 0d3e0e66-fbec-4bab-a070-f27f36f843e0 'killed' while waiting for 'active'
2014-07-23 11:02:18.129 |     
2014-07-23 11:02:18.129 | 
2014-07-23 11:02:18.129 | Captured pythonlogging:
2014-07-23 11:02:18.129 | ~~~~~~~~~~~~~~~~~~~~~~~
2014-07-23 11:02:18.129 |     2014-07-23 10:56:39,064 27125 INFO     [tempest.common.rest_client] Request (CreateRegisterImagesTest:test_register_http_image): 200 POST http://127.0.0.1:5000/v2.0/tokens
2014-07-23 11:02:18.129 |     2014-07-23 10:56:39,291 27125 INFO     [tempest.common.rest_client] Request (CreateRegisterImagesTest:test_register_http_image): 201 POST http://127.0.0.1:9292/v1/images 0.226s
2014-07-23 11:02:18.129 |     2014-07-23 10:56:39,397 27125 INFO     [tempest.common.rest_client] Request (CreateRegisterImagesTest:test_register_http_image): 200 HEAD http://127.0.0.1:9292/v1/images/0d3e0e66-fbec-4bab-a070-f27f36f843e0 0.105s
2014-07-23 11:02:18.129 |     2014-07-23 10:56:41,595 27125 INFO     [tempest.common.rest_client] Request (CreateRegisterImagesTest:test_register_http_image): 200 HEAD http://127.0.0.1:9292/v1/images/0d3e0e66-fbec-4bab-a070-f27f36f843e0 0.195s
2014-07-23 11:02:18.129 |     2014-07-23 10:56:42,597 27125 INFO     [tempest.services.image.v1.json.image_client] Value transition from "queued" to "killed"in 2 second(s).

The glance-api logs from around that time are not particularly helpful:

http://logs.openstack.org/10/108410/2/check/check-tempest-dsvm-postgres-
full/4496d7e/logs/screen-g-api.txt.gz#_2014-07-23_10_56_40_704

http://logs.openstack.org/10/108410/2/check/check-tempest-dsvm-postgres-
full/4496d7e/logs/screen-g-reg.txt.gz#_2014-07-23_10_56_40_797

** Affects: glance
     Importance: Undecided
         Status: New

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

Title:
  gate failure with
  tempest.api.image.v1.test_images.CreateRegisterImagesTest.test_register_http_image

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  In review https://review.openstack.org/#/c/108410/ I get a failure
  with check-tempest-dsvm-postgres-full.

  (note this is not a duplicate of
  https://bugs.launchpad.net/glance/+bug/1247194 )

  Presumably this is a timeout, or something getting ahead of something
  else. Reporting to be a good boy.

  Logs and links to logs below:

  2014-07-23 11:02:18.128 | ==============================
  2014-07-23 11:02:18.128 | Failed 1 tests - output below:
  2014-07-23 11:02:18.128 | ==============================
  2014-07-23 11:02:18.128 | 
  2014-07-23 11:02:18.128 | tempest.api.image.v1.test_images.CreateRegisterImagesTest.test_register_http_image[gate]
  2014-07-23 11:02:18.128 | ----------------------------------------------------------------------------------------
  2014-07-23 11:02:18.128 | 
  2014-07-23 11:02:18.128 | Captured traceback:
  2014-07-23 11:02:18.128 | ~~~~~~~~~~~~~~~~~~~
  2014-07-23 11:02:18.128 |     Traceback (most recent call last):
  2014-07-23 11:02:18.128 |       File "tempest/api/image/v1/test_images.py", line 79, in test_register_http_image
  2014-07-23 11:02:18.128 |         self.client.wait_for_image_status(image_id, 'active')
  2014-07-23 11:02:18.129 |       File "tempest/services/image/v1/json/image_client.py", line 295, in wait_for_image_status
  2014-07-23 11:02:18.129 |         status=status)
  2014-07-23 11:02:18.129 |     ImageKilledException: Image 0d3e0e66-fbec-4bab-a070-f27f36f843e0 'killed' while waiting for 'active'
  2014-07-23 11:02:18.129 |     
  2014-07-23 11:02:18.129 | 
  2014-07-23 11:02:18.129 | Captured pythonlogging:
  2014-07-23 11:02:18.129 | ~~~~~~~~~~~~~~~~~~~~~~~
  2014-07-23 11:02:18.129 |     2014-07-23 10:56:39,064 27125 INFO     [tempest.common.rest_client] Request (CreateRegisterImagesTest:test_register_http_image): 200 POST http://127.0.0.1:5000/v2.0/tokens
  2014-07-23 11:02:18.129 |     2014-07-23 10:56:39,291 27125 INFO     [tempest.common.rest_client] Request (CreateRegisterImagesTest:test_register_http_image): 201 POST http://127.0.0.1:9292/v1/images 0.226s
  2014-07-23 11:02:18.129 |     2014-07-23 10:56:39,397 27125 INFO     [tempest.common.rest_client] Request (CreateRegisterImagesTest:test_register_http_image): 200 HEAD http://127.0.0.1:9292/v1/images/0d3e0e66-fbec-4bab-a070-f27f36f843e0 0.105s
  2014-07-23 11:02:18.129 |     2014-07-23 10:56:41,595 27125 INFO     [tempest.common.rest_client] Request (CreateRegisterImagesTest:test_register_http_image): 200 HEAD http://127.0.0.1:9292/v1/images/0d3e0e66-fbec-4bab-a070-f27f36f843e0 0.195s
  2014-07-23 11:02:18.129 |     2014-07-23 10:56:42,597 27125 INFO     [tempest.services.image.v1.json.image_client] Value transition from "queued" to "killed"in 2 second(s).

  The glance-api logs from around that time are not particularly
  helpful:

  http://logs.openstack.org/10/108410/2/check/check-tempest-dsvm-
  postgres-
  full/4496d7e/logs/screen-g-api.txt.gz#_2014-07-23_10_56_40_704

  http://logs.openstack.org/10/108410/2/check/check-tempest-dsvm-
  postgres-
  full/4496d7e/logs/screen-g-reg.txt.gz#_2014-07-23_10_56_40_797

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1347692/+subscriptions
Follow ups

[Bug 1347692] [NEW] gate failure with tempest.api.image.v1.test_images.CreateRegisterImagesTest.test_register_http_image
From: Chris Dent, 2014-07-23
References

[Bug 1347692] [NEW] gate failure with tempest.api.image.v1.test_images.CreateRegisterImagesTest.test_register_http_image
From: Chris Dent, 2014-07-23