Bug 1019056

Summary: Clarify status of post_s390_reboot kickstart snippet
Product: [Retired] Beaker Reporter: Nick Coghlan <ncoghlan>
Component: DocAssignee: beaker-dev-list
Status: CLOSED WONTFIX QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.15CC: qwan, tools-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-21 14:15:22 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:
Embargoed:

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 :)