Tempest results not machine consumable

[Hugh Saunders]

Currently the OSAD scripts for running tempest output the results as part of the test run log. These results are easily burried in a large log file and can be difficult to compare across runs.

I propose that the tempest scripts create a junit xml log file that can be consumed by other systems (such as jenkins).

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/197512
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=784a29b1138c72edbadd8421850605c50bb3ff95
Submitter: Jenkins
Branch: kilo

commit 784a29b1138c72edbadd8421850605c50bb3ff95
Author: Hugh Saunders <email address hidden>
Date: Thu Jun 11 11:35:39 2015 +0100

    Create Junit XML Report from tempest run

    Tempest results are currently written to stdout as part of a test run.
    This output is difficult to parse. This patch adds steps to generate an
    XML report, and make this report available in /tmp on a physical host.

    The report is copied to a physical host so that external systems that do
    not have knowledge of the container inventory can retrieve the report,
    for example Jenkins.

    * Add pip packages python-subunit and junitxml to tempest venv, needed
      to convert the subunit stream stored in testrepository to junit XML.

    * openstack_tempest_gate:
        After a tempest run completes, the subunit stream is extracted from
        the testrepository, converted to junit XML and written to /tmp in
        the utility container running the tests.

    * run-tempest.sh
        After running openstack_tempest_gate, retrieve XML results and write
        them to /tmp on the host.

    Change-Id: I897024f545dd2a90f80b0d5c0aa558f335dc963a
    Closes-Bug: #1464686
    (cherry picked from commit 8a7d5179d66cd43c3f49cec6a764f1073232e6f3)

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.