yahoo-eng-team team mailing list archive

[jichenjc <jichenjc@xxxxxxxxxx>]

accordingly to avoid description, looks like this is a tempest issue?

** Project changed: nova => tempest

-- 
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/1713163

Title:
  test_delete_saving_image fails because image hasn't transitioned to
  SAVING

Status in tempest:
  New

Bug description:
  http://logs.openstack.org/33/440933/4/check/gate-tempest-dsvm-neutron-
  linuxbridge-ubuntu-xenial/ebfa453/logs/testr_results.html.gz

  
  Traceback (most recent call last):
    File "tempest/api/compute/images/test_images.py", line 48, in test_delete_saving_image
      wait_until='SAVING')
    File "tempest/api/compute/base.py", line 301, in create_image_from_server
      image_id, wait_until)
    File "tempest/common/waiters.py", line 179, in wait_for_image_status
      raise lib_exc.TimeoutException(message)
  tempest.lib.exceptions.TimeoutException: Request timed out
  Details: (ImagesTestJSON:test_delete_saving_image) Image 93090479-409d-49f9-b2d3-2bc11a40f967 failed to reach SAVING state (current state ACTIVE) within the required time (196 s).

  
  I briefly looked at the test case, and it seems to me that it may happen when the image snapshot is produced quicker than tempest being able to catch the intermittent transition. If so, the test case may need a refinement to check that a snapshot was produced and not that the state was in SAVING for some time.

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