Bug 1019056 - Clarify status of post_s390_reboot kickstart snippet
Clarify status of post_s390_reboot kickstart snippet
Status: NEW
Product: Beaker
Classification: Community
Component: Doc (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: beaker-dev-list
Depends On:
  Show dependency treegraph
Reported: 2013-10-15 01:45 EDT by Nick Coghlan
Modified: 2018-02-05 19:41 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nick Coghlan 2013-10-15 01:45:15 EDT
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.