Only first Tempest gate result retrieved after multiple tests

Bug #1476793 reported by Julian Montez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Medium
Julian Montez
Kilo
Fix Released
Medium
Jesse Pretorius
Trunk
Fix Released
Medium
Julian Montez

Bug Description

Running the `/opt/openstack_tempest_gate.sh` script on the designated Tempest utility container only delivers the first testrepository subunit stream.

All test results are archived, with filenames incrementing from zero, but the first result is hardcoded to be copied for a deployment node to retrieve (https://github.com/stackforge/os-ansible-deployment/blob/39409db9b9caea199fd61110f348c0be209e6754/playbooks/roles/os_tempest/templates/openstack_tempest_gate.sh.j2#L189-L190).

Using the `testr` CLI, the last result can be used in conjunction with its own subunit stream utility to ensure the latest results are delivered to an end user.

Julian Montez (jpmontez)
Changed in openstack-ansible:
assignee: nobody → Julian Montez (jpmontez)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (master)

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

Changed in openstack-ansible:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (master)

Reviewed: https://review.openstack.org/204214
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=3a94890367ea2fcd69e85980623cb6f61a60515b
Submitter: Jenkins
Branch: master

commit 3a94890367ea2fcd69e85980623cb6f61a60515b
Author: Julian Montez <email address hidden>
Date: Tue Jul 21 11:27:21 2015 -0500

    Parse latest Tempest results

    Output latest test run results as a subunit stream using testr's
    built-in utility.

    Closes-Bug: #1476793
    Change-Id: Ib7afd26fe368303ac18ddc3436ee90a02301557f

Changed in openstack-ansible:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (kilo)

Fix proposed to branch: kilo
Review: https://review.openstack.org/204948

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (kilo)

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

commit 1d0ff35bee3f6a5a444ceb9e583286e30a517549
Author: Julian Montez <email address hidden>
Date: Tue Jul 21 11:27:21 2015 -0500

    Parse latest Tempest results

    Output latest test run results as a subunit stream using testr's
    built-in utility.

    Closes-Bug: #1476793
    Change-Id: Ib7afd26fe368303ac18ddc3436ee90a02301557f
    (cherry picked from commit 3a94890367ea2fcd69e85980623cb6f61a60515b)

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.11

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

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

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

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.