Bug 439129
| Summary: | When I escalate the result of test for RHEL5.1(dom0), memory error message is displayed. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Ready Certification Tests | Reporter: | Issue Tracker <tao> | ||||
| Component: | web site | Assignee: | XINSUN <xisun> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 1.0 | CC: | tao, ykun | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | (2.18rh) 2008/05/23 push | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-06-23 07:43:15 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Issue Tracker
2008-03-27 04:41:28 UTC
Description of problem: When I update the result rpm file of PQ520A-RHEL5.1(dom0) for escalation, following error message is displayed and I failed to escalate. --------------------------------------------------------- Failures Detected FAILED: Incorrect memory amount You can still submit the certification but it will not be automatically certified and will require review from a Red Hat employee. --------------------------------------------------------- In this test, MEMORY test is passed. What kind of problem is there in this rpm file? hts version is as follows. # rpm -q hts hts-5.1-16.el5 How reproducible: Always Steps to Reproduce: 1) Escalate with the attached rpm file. Actual results: Escalation is rejected. Expected results: Escalation is submitted. Additional info: None This event sent from IssueTracker by mmatsuya [Fujitsu-Certification] issue 170663 File uploaded: hts-Red_Hat-ParaVirt_Guest-Tikanga_ia64_results-2.noarch.rpm This event sent from IssueTracker by mmatsuya [Fujitsu-Certification] issue 170663 it_file 125100 Severity changed: 3 -> 2. Reason: If this problem is not solved, PQ520A is not certified before PQ520A release. So business impact is too big, so I want to solve the problem rapidly.. Severity set to: High This event sent from IssueTracker by mmatsuya [Fujitsu-Certification] issue 170663 *** Bug 439130 has been marked as a duplicate of this bug. *** Hi, I have checked this bug, The caused reason is that the max value of test memory amount which hwcert catalog limits is 65536 in the "limits" file, while your system's memory amount is 122803. We will fix it via enlarging and modifying the maxmem value in the "limits" file by handy later (Waiting sys-admins who have the permissions for doing that.). You can use below method as emergency: Step 1. Click the "Provide Manually" for Product Data Source to create a cert. and fill the "Make" and "Model",etc. then create a cert. (Create a cert without the rpm package.) Step 2. When cert is created, then upload the rpm package as "Upload Results Package" in the "Review" section. Thank you for your answer. I succeeded to eslalate result rpm file of RHEL4.6 by using method you show. By the way, I tested PQ580A which has same memory (256GB) as PQ520A, but I succeeded to escalate. Why error is displayed in only PQ520A? Regards, Hideto Yamada. This event sent from IssueTracker by mmatsuya issue 170664 Created attachment 302316 [details] Adjust the max value of the memory amount Rob and Yk, I have update the limits.xml according to "compare" page: http://www.redhat.com/rhel/compare/ Pls help me to review if the max memory amount value is right. Thanks a lot. Patch has been summited into cvs. Addressing to update the limits.xml according to the push of rhel6' or the update of http://www.redhat.com/rhel/compare/. If anyone found this bug appears again, pls feel free to reopen this bug. Thanks a lot! Best Regards! Nicho |