| Summary: | "...is not an official release.." when uploading results created with latest hwcert packages | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Christian Horn <chorn> | ||||
| Component: | Hardware Catalog | Assignee: | Yu Shao <yshao> | ||||
| Status: | CLOSED EOL | QA Contact: | |||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 1.6.5 | CC: | hwcert-catalog, jkachuck, jread, pmao, rlandry, yshao | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-06-30 09:15:32 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
Christian Horn
2013-12-03 15:52:56 UTC
This should be fixed with new test suite version being added to admin page. So I will close it. This occurs again for hwcert-client-1.6.5.2-20140416 as of this morning, attaching screenshot. The issue occurs for the same partner. It would be great if we could verify such things that occured once, kind of what we do for bz's in our errata RPM packages, to prevent this. I am setting sev/prio to urgent as "use the older version" does not seem like a viable workaround here. The partner would have to run other tests then probably also again with the other version, maybe even open the whole cert again. If there are any workarounds, please let us know. Created attachment 889552 [details]
screenshot
The hotfix is live, hwcert-client-1.6.5.2-20140416 can be accepted now. Thanks for the update. As this occurred now already 2 times, and the same partner was always hit by this, did we undertake any steps to prevent such in the future? For bz's in code we write tests to automatically verify conditions in the future. Already next week an errata for hwcert-client is about to be released. |