Bug 1019056 - Clarify status of post_s390_reboot kickstart snippet
Summary: Clarify status of post_s390_reboot kickstart snippet
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: Doc
Version: 0.15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-15 05:45 UTC by Nick Coghlan
Modified: 2020-10-21 14:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-21 14:15:22 UTC
Embargoed:


Attachments (Terms of Use)

Description Nick Coghlan 2013-10-15 05:45:15 UTC
The post_s390_snippet is enabled by default in all current Beaker kickstarts, but:

1. A comment in the kickstart claims the issue it deals with was fixed in RHEL5-U3

2. The documentation claims the snippet is broken (http://beaker-project.org/docs/admin-guide/kickstarts.html#kickstart-snippets)


If the comment is accurate, the kickstarts for Fedora and more recent versions of RHEL should not load the snippet.

If the docs are accurate (which seems unlikely, given that s390 provisioning currently works), then the snippet shouldn't be loaded at all.

If either the docs or the comment are inaccurate, then they should be fixed :)


Note You need to log in before you can comment on or make changes to this bug.