| Summary: | hwcert-client no longer logging "Test Parameters" | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Yunlong Xue <yxue> | ||||||
| Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.6 | CC: | bbrock, gnichols, qcai, rlandry | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | hwcert-client 1.6.5-20131210 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1038354 (view as bug list) | Environment: | |||||||
| Last Closed: | 2014-05-21 19:18:51 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Yunlong Xue
2013-10-08 05:22:41 UTC
This was changed to be printed only in debug modes. Do we want to restore it in 1.6.5 and.or 1.7.0? (In reply to Greg Nichols from comment #1) > This was changed to be printed only in debug modes. Do we want to restore > it in 1.6.5 and.or 1.7.0? Yes, can we put them in a <parameters> tag or similar? We could then easily control visibility in the catalog if it becomes noisy. This makes sense. Created attachment 832907 [details]
patch adding <parameters> to <run> to log Test Parameters in XML
Created attachment 834838 [details]
additional patch storing parameters as name/value pairs
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. http://rhn.redhat.com/errata/RHBA-2014-0532.html |