Bug 1538831 - rhcert-ci junit output is not consistent with what has been actually run
Summary: rhcert-ci junit output is not consistent with what has been actually run
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Greg Nichols
QA Contact: rhcert qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-25 23:11 UTC by Gonéri Le Bouder
Modified: 2018-02-01 09:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-01 09:17:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0261 0 normal SHIPPED_LIVE Red Hat Certification bug fix and enhancement update 2018-02-01 14:17:39 UTC

Description Gonéri Le Bouder 2018-01-25 23:11:03 UTC
Description of problem:


[root@directorvm stack]# rhcert-ci run --test supportable --test self_check --test cinder_volumes --test cinder_consistency_groups --debug low
[root@directorvm stack]# rhcert-ci print --format junit|grep supportable
</testcase><testcase classname="supportable" name="supportable" time="0.00">
<skipped>supportable not activated</skipped>

Supportable was enabled and returned a 'REVIEW' status.

redhat-certification-openstack-5.6-20180110.el7.noarch
redhat-certification-5.6-20180110.el7.noarch
redhat-certification-backend-5.6-20180110.el7.noarch

Comment 1 Gonéri Le Bouder 2018-01-25 23:23:57 UTC
I don't have the problem if I remove the --format junit:

[root@directorvm stack]# rhcert-ci print|grep supportable
supportable     - REVIEW

Comment 2 Gonéri Le Bouder 2018-01-26 17:05:25 UTC
The problem is in reportjunit.py. There is no support for the was where summary=='REVIEW'.

Comment 6 errata-xmlrpc 2018-02-01 09:17:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0261


Note You need to log in before you can comment on or make changes to this bug.