Bug 1525665
| Summary: | Unable to submit test id's for server cert testplan components through rh-cert tool | ||
|---|---|---|---|
| Product: | Red Hat Certification Program | Reporter: | HPE Server Cert <hpe_rh_cert> |
| Component: | redhat-certification | Assignee: | Rajasi <rajkulka> |
| Status: | CLOSED ERRATA | QA Contact: | rhcert qe <rhcert-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 1.0 | CC: | brose, jkachuck, jweng, mark.coskey, rlandry |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-01-15 08:50:56 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: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1105196 | ||
|
Description
HPE Server Cert
2017-12-13 20:07:13 UTC
We checked both a remote login to the rh-cert server and accessing the interface while logged onto the host. My understanding is you want to input test ID for leveraging? right ? rhcert now has a bug for leverage test/component ID. If you want to leverage the results, please tell us the test/component ID and the corresponding test plan in the cert, cert ops will help to do that before this bug is fixed. Jianwei, Correct, in the rh-cert submission browser interface we need a way to enter leverage ids in the test plan like the old submission interface. Right now we can only list test ids in the dialog section for the reviewer which is cumbersome. Please confirm RH is working on a solution. Thanks, Mark Yes, we have reproduced the bug and it will be fixed in redhat-certification-5.6. 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:0086 |