Stack traces from tempest aren't showing up in tempest.txt log

[Matt Riedemann]

We used to get stack traces in the tempest.txt log which was nice so we could do multiline logstash queries for elastic-recheck, but we don't get that now.

For example, this trace in the console log:

http://logs.openstack.org/05/128905/1/check/gate-tempest-dsvm-ceilometer-mongodb-full/1d0f357/console.html#_2014-10-16_13_25_47_032

Is not in the tempest.txt log:

http://logs.openstack.org/05/128905/1/check/gate-tempest-dsvm-ceilometer-mongodb-full/1d0f357/logs/tempest.txt.gz

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/130792

[OpenStack Infra (hudson-openstack)]

Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/130792
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Yaroslav Lobankov (ylobankov)]

The proposed patch (https://review.openstack.org/130792) is abandoned, but the current status of the bug is "In progress". So moving the status to "New".

[Ghanshyam Mann (ghanshyammann)]

@Matt Riedemann, is this issue still exist?

If it was tearDownClass issue, now exceptions are logged correctly- https://github.com/openstack/tempest/blob/master/tempest/test.py#L303

Please let us know if it was somewhere else as I cannot access mentioned logs to know the original problem.

[Matt Riedemann (mriedem)]

I think this was fixed inadvertently. I think we have at least one query in elastic-recheck that relies on a stack trace in tempest.txt for the failure and that has hits so this must be working.