AttributeError: 'BadRequest' object has no attribute 'status_code'

[Davanum Srinivas (DIMS)]

I see the following stack traces

ft26.1: tearDownClass (tempest.scenario.test_minimum_basic.TestMinimumBasicScenario)_StringException: Traceback (most recent call last):
  File "tempest/scenario/manager.py", line 264, in tearDownClass
    if e.__class__.__name__ == 'NotFound' or e.status_code == 404:
AttributeError: 'BadRequest' object has no attribute 'status_code

Example log:
http://logs.openstack.org/04/63304/5/check/check-tempest-dsvm-postgres-full/010c428/testr_results.html.gz

logstash shows 129 hits in last 48 hours with query "AttributeError: 'BadRequest' object has no attribute 'status_code'"

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

[David Kranz (david-kranz)]

This should be fixed by https://review.openstack.org/#/c/63144/

[Sean Dague (sdague)]

So this isn't a critical bug, it's not actually causing gate resets, it only gets seen once other failures happen.