tempest should log req-id for failed tests to make debugging easier

[Joe Gordon]

even though nova returns the req-id of each call, tempest doesn't record them. These req-id are returned under 'x-compute-request-id' and can be used to search the nova logs to find the logs related to that request.

If the req-ids are printed to stdout testr will record that information and only print stdout for failed tests.

[OpenStack Infra (hudson-openstack)]

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

[Attila Fazekas (afazekas)]

We recently switched to oslo logging. I do not really follow why to use print if we have loggers.

Normally python programs are using loggers for printing.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/41934
Committed: http://github.com/openstack/tempest/commit/e5423911e117bf760fc702c03fd6a40af4d60048
Submitter: Jenkins
Branch: master

commit e5423911e117bf760fc702c03fd6a40af4d60048
Author: Matthew Treinish <email address hidden>
Date: Tue Aug 13 18:07:31 2013 -0400

    Log request ids from glance and nova

    This commit adds an option a log message at the info level to
    print the req-id returned from nova and glance. This can be useful
    when trying to debug test failures because it provides you with a
    unique identifier in the nova and glance logs for request
    information. This is done at the info level so that it will be
    included in the subunit stream to be printed out during a test
    failure to help with debugging.

    Fixes bug 1210639

    Change-Id: I819f94c538e6a15732dbb4b5c2dafdc270e0b2b4