Bug 809704 - beaker scripts in custom kickstart don't log to /dev/console
Summary: beaker scripts in custom kickstart don't log to /dev/console
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-04 06:33 UTC by Marian Ganisin
Modified: 2019-05-22 13:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-26 06:41:29 UTC
Embargoed:

Attachments (Terms of Use)

Description Marian Ganisin 2012-04-04 06:33:27 UTC 
Beaker specific post-installation scripts in kickstart log into /dev/console. This isn't true in case of custom kickstart defined via <kickstart/>. Appended beaker specific scripts do not have --log defined.
Comment 1 Dan Callaghan 2012-05-21 04:41:45 UTC 
This is made slightly more awkward by the fact that RHEL3 does not support --log so we have to put the scriptlet in a subshell and redirect it for RHEL3. But it is still doable.
Comment 2 Dan Callaghan 2012-05-21 05:10:53 UTC 
On Gerrit: http://gerrit.beaker-project.org/1076
Comment 4 Dan Callaghan 2012-06-26 06:41:29 UTC 
Beaker 0.9.0 has been released.
Note You need to log in before you can comment on or make changes to this bug.