yahoo-eng-team team mailing list archive

[OpenStack Infra <1411708@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/147895
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=41a74431a234b59b3d3c78057b3fe2fe3c351e9d
Submitter: Jenkins
Branch:    master

commit 41a74431a234b59b3d3c78057b3fe2fe3c351e9d
Author: Matt Riedemann <mriedem@xxxxxxxxxx>
Date:   Fri Jan 16 07:43:07 2015 -0800

    Use create_test_server in test_max_image_meta_exceed_limit
    
    When this fails it's just a MismatchError in the logs so it's hard to
    fingerprint this kind of race failure in logstash, especially since the
    name of the test server is just 'test'.
    
    Change to use the create_test_server method from the base class so the
    instance name has the class name in it which would make this easier to
    fingerprint in the result of an intermittent failure.
    
    This is doubly useful since if this fails we're leaking a server
    resource. By using create_test_server, if the assertion fails then at
    least the base class is tracking the server created and will delete it
    on tear down.
    
    Related-Bug: #1411708
    
    Change-Id: Ib015442a4d89dfcbb68438fe31d6fda719ddd011


** Changed in: tempest
       Status: In Progress => 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/1411708

Title:
  AbsoluteLimitsNegativeTestJSON.test_max_image_meta_exceed_limit fails
  to fail

Status in OpenStack Compute (Nova):
  Invalid
Status in Tempest:
  Fix Released

Bug description:
  This is a negative test that is supposed to fail with an over-quota
  exception when creating the server but it looks like it's successfully
  creating the server request at times:

  http://logs.openstack.org/00/135700/45/check/check-tempest-dsvm-
  postgres-full/3bb3614/console.html#_2015-01-16_00_57_07_456

  So there is some race here.

  http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwidGVtcGVzdC5hcGkuY29tcHV0ZS5saW1pdHMudGVzdF9hYnNvbHV0ZV9saW1pdHNfbmVnYXRpdmUuQWJzb2x1dGVMaW1pdHNOZWdhdGl2ZVRlc3RKU09OLnRlc3RfbWF4X2ltYWdlX21ldGFfZXhjZWVkX2xpbWl0XCIgQU5EIG1lc3NhZ2U6XCJGQUlMRURcIiBBTkQgdGFnczpcImNvbnNvbGVcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQyMTQyMTQyNTU2N30=

  31 hits in 7 days, all check queue according to that but it's on
  multiple changes.

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