Bug 1795234 - RFE: add kickstart metadata keyword for firstboot
Summary: RFE: add kickstart metadata keyword for firstboot
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: develop
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 27.1
Assignee: Martin Styk
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-27 13:58 UTC by Jeff Bastian
Modified: 2020-01-28 10:32 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-28 10:32:05 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Beaker Project Gerrit 6746 0 None MERGED feat: add option to enable firstboot in ks 2020-02-28 14:14:33 UTC

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


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