Bug 807991
Summary: | Unexpected package definition: -readahead | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Marian Ganisin <mganisin> |
Component: | lab controller | Assignee: | Qixiang Wan <qwan> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Dan Callaghan <dcallagh> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 0.8 | CC: | bpeck, dcallagh, llim, mcsontos, qwan, rmancy, stl |
Target Milestone: | 0.12 | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | Kickstart | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-04-11 04:55:47 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: |
Description
Marian Ganisin
2012-03-29 09:59:40 UTC
See the release notes of the bug 561486 - it is solved exactly by disabling readahead. We have to test installation of custom package sets, therefore we need full control over packages section. I have no problem with such hacks in common beaker tasks. However if there is custom kickstart with %packages section defined it has to stay unaltered, otherwise we can't use beaker for this kind of testing. Additionally there doesn't seem to be any reason to modify RHEL5 kickstart based on RHEL6 bug as it happened here for example: https://beaker.engineering.redhat.com/jobs/223209 Bulk reassignment of issues as Bill has moved to another team. We could change our workaround to be to just turn off readhead, as described in bug 561486, instead of removing it. And I agree the workaround should only apply in RHEL6. on gerrit: http://gerrit.beaker-project.org/#/c/1744/ Verified that -readahead is absent from %packages, and that the sysconfig snippet appears only on RHEL6, and that nothing bad seems to have happened. Beaker 0.12 has been released. |