Bug 1795234

Summary: RFE: add kickstart metadata keyword for firstboot
Product: [Retired] Beaker Reporter: Jeff Bastian <jbastian>
Component: generalAssignee: Martin Styk <mastyk>
Status: CLOSED NEXTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: developCC: bpeck, cbouchar, jkriz, mastyk, pbunyan
Target Milestone: 27.1Keywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-28 10:32:05 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 Jeff Bastian 2020-01-27 13:58:05 UTC
Description of problem:
Please update the 'default' kickstart template to use a kickstart metadata keyword for the firstboot command, for example:

  firstboot {{ firstboot|default('--disabled') }}

This will allow us to do QE testing of the initial-setup tool with ks_meta="firstboot=--enabled".  At the moment, we have to write a full <kickstart>...</kickstart> section with the entire top portion of a kickstart file (everything before %packages) just override the one firstboot command.

Version-Release number of selected component (if applicable):
Beaker 26.6