Bug 1734744 - Installation from tar image doesn't preserve custom kernel commandline options from blueprint
Summary: Installation from tar image doesn't preserve custom kernel commandline option...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lorax-composer
Version: 7.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Jiri Kortus
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-31 11:03 UTC by Jiri Kortus
Modified: 2019-07-31 15:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-31 15:36:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jiri Kortus 2019-07-31 11:03:57 UTC
Description of problem:
After creating a tar image using a blueprint that contains specific settings for custom kernel command line option, and then installing the image via kickstart containing a liveimg command, the installed system doesn't contain the custom settings in bootloader configuration.

This might be anaconda's fault as well, however in the first place it seems that the resulting tar image doesn't even carry those custom options in any way, so  Anaconda can't even use them when creating bootloader configuration.

Version-Release number of selected component (if applicable):
lorax-composer-19.7.35-1

How reproducible:
100%

Steps to Reproduce:
1. Prepare a blueprint containing a custom bootloader parameter, e. g.:
...
[customizations.kernel]
append = "custom_cmdline_arg"

2. Push the blueprint to lorax-composer repo and create a tar image with lorax-composer.
3. Install the resulting tar image using kickstart.
4. Inspect the installed system bootloader configuration.

Actual results:
Neither GRUB configuration nor /etc/default/grub contains the custom option.

Expected results:
The custom option(s) is present in all necessary places in the system and system boots up using this option.

Comment 2 Brian Lane 2019-07-31 15:36:21 UTC
This isn't a bug -- the tar doesn't have a bootloader like a disk image, so there is no place for the extra cmdline args to be put. You have to specify them in the final kickstart you create to install the tar.

Comment 3 RHEL Program Management 2019-07-31 15:36:25 UTC
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.


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