Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693916 - We couldn't save the correct logs by commandline. (P.S. We tested the SUT by commandline)
Summary: We couldn't save the correct logs by commandline. (P.S. We tested the SUT by...
Status: NEW
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification-hardware
Version: 1.0
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: brose
QA Contact: rhcert qe
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-29 02:41 UTC by amanda_lin
Modified: 2019-04-02 16:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
step_1_to_4 (deleted)
2019-03-29 02:41 UTC, amanda_lin
no flags Details

Description amanda_lin 2019-03-29 02:41:42 UTC
Created attachment 1549276 [details]

Description of problem:
If the first test case failed, the following test result will collect the log with first test case. 

for instance, we run "usb2" test first and get the fail result, than we run "info" test right after "usb2" test. When we collect the "info" test log after it passed, we would still getting the "usb2" test log instead of "info" test log.

The workaround we have is to type "rhcert-cli clean all" to clean all logs or generated logs by web.

Version-Release number of selected component (if applicable):
testkit version: rhcert v6.5 - 6.7
OS: RHEL7 & 8

How reproducible:
It happened after got the result fail.

Steps to Reproduce:
1. First, we ran the test item – “usb2”, and then let it be failed on purpose.
2. Saved the failed “usb2” log successfully.
3. Then, we ran the test item – “info” by the command rhcert-cli run -t info and it passed.
4. We tried to save the passed ”info” log, but it saved the same previous “usb2” log instead.

Actual results:
save the "usb2" log

Expected results:
save the "info" log

Additional info:
Attached file is the screenshot follow steps.

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