Bug 485212
| Summary: | plan --add command may end up with irrelevant UDI information | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Greg Nichols <gnichols> |
| Component: | Test Suite (harness) | Assignee: | Greg Nichols <gnichols> |
| Status: | CLOSED ERRATA | QA Contact: | Guangze Bai <gbai> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.3 | CC: | averma, czhang, rlandry, yshao, yuchen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
In v7 1.2, "v7 plan --add" command may end up with irrelevant UDI information in cpuscaling test. This issue has been fixed in v7 1.3, now cpuscaling test is no longer associated with a logical CPU device, only one cpuscaling instance will be executed during testing, thus no irrelevant UDI information any more.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-05-09 16:15: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: | |||
| Bug Depends On: | 488129 | ||
| Bug Blocks: | |||
|
Description
Greg Nichols
2009-02-12 12:42:53 UTC
The problem is that when --device is used, HTS tries to associate the test with a device discovered by HAL (or Kudzu on RHEL4). Since there is no universal attribute for a "logical" device name, it tries to match the provided string against any attribute value. If the string passed in via --device is one or two characters, as in this example, it could match any device. The cpuscaling test does not use the association at all, only the literal value passed in by --device. This situation is difficult to improve with out compromising the utility of the plan --add command as a work-around. One possible heuristic would be to only attempt device matches if 3 or more characters were provided. That would allow the addition of the storage command for "sda", or the network command for "eth2", but prevent the spurious association when "1" was passed in as the device for the cpuscaling test. I complete and correct fix would be to encode knowledge in the tests about which attributes defined "logical" device name. For the cpuscaling test, it would state None to indicate that it didn't require a device association. The storage test could specify that it needed to match a substring of the block.device attribute under HAL, and the "device" property under Kudzu. Alternatively, we could not fix this bug, as the resulting strings in the print command really are just a slightly-confusing cosmetic issue, in the context of a command that is only provided as a work-around for other RHEL or HTS bugs. Just an idea, since --add and subsequently --device means we're in manual try to do what the user tells us since auto detection didn't work or it's values are not desired mode, perhaps we could require both --udi and --device as input for all --add cases? This would require more of the user in these cases to include sometimes requiring a 'none' value where it's not needed/desired but it would also clean up the cosmetic issue and ensure that manual test plan definitions are fully defined even if incorrectly by the user at least establishing a full 'do as I say' manual mode? ...the point of the idea being to minimize the time spent coding on a cosmetic issue while still fixing the bug and at least partially improving the user experience? Bug 488129 proposes a solution that could be extended to fix this bug as well, by removing code that attempts to associate a device with a test, and replacing it with a manual prompt in the test's "verify" phase.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
In v7 1.2, "v7 plan --add" command may end up with irrelevant UDI information in cpuscaling test. This issue has been fixed in v7 1.3, now cpuscaling test is no longer associated with a logical CPU device, only one cpuscaling instance will be executed during testing.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-In v7 1.2, "v7 plan --add" command may end up with irrelevant UDI information in cpuscaling test. This issue has been fixed in v7 1.3, now cpuscaling test is no longer associated with a logical CPU device, only one cpuscaling instance will be executed during testing.+In v7 1.2, "v7 plan --add" command may end up with irrelevant UDI information in cpuscaling test. This issue has been fixed in v7 1.3, now cpuscaling test is no longer associated with a logical CPU device, only one cpuscaling instance will be executed during testing, thus no irrelevant UDI information any more.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0497.html |