Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRanjith Rajaram
2018-12-04 06:19:55 UTC
Description of problem:
As per RHEL8 documentation [1], we prefer composer-gui over cli. When using composer-gui, qcow2 image creation is successful. VM boots successfully using the custom image but unfortunately no detail in documentation or an option in the composer-gui to include a username or add any custom settings.
Adding an option directly in qcow2.ks( /usr/share/lorax/composer/qcow2.ks) is reflected but this will affect all the builds
Example output
composer-cli blueprints show podman
name = "podman"
description = "demo test"
version = "0.0.2"
modules = []
groups = []
[[packages]]
name = "podman"
version = "0.10.1.3"
As per the uptream doc, user's can be included in the blueprint
https://weldr.io/lorax/lorax-composer.html
currently composer-gui only allows to select packages and build images. We need options to customize blueprints to include additional information
Version-Release number of selected component (if applicable):
lorax-templates-rhel-8.0-19.el8.noarch
lorax-28.14.16-1.el8.x86_64
lorax-composer-28.14.16-1.el8.x86_64
lorax-lmc-novirt-28.14.16-1.el8.x86_64
lorax-templates-generic-28.14.16-1.el8.x86_64
[root@localhost ~]#
How reproducible:
Always
Steps to Reproduce:
1. Attempt to create a blueprint and to add a user
2.
3.
Actual results:
If you are creating a qcow2 image via composer-gui, there are no option to mention the custom username or configure sudo access for the user. Resulting qcow2 image cannot be used.
Expected results:
Option to include custom information like username, partition etc
Additional info:
[1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html/installing_and_deploying_rhel/building-custom-system-images-with-composer_graphical-installation
It seems to be possible from command line. Below worked.
Add
[[customizations.user]]
name = "admin"
description = "Administrator account"
password = "redhat"
to an blueprint file and use the below command
Example blueprint
name = "rhel8testcustomusername"
description = "test qcow2"
version = "0.0.2"
modules = []
groups = []
[[packages]]
name = "findutils"
version = "4.6.0"
[[customizations.user]]
name = "admin"
description = "Administrator account"
password = "redhat"
Execute the command
composer-cli blueprints push /root/blueprint.toml
USe this blueprint to create custom images.
final-kickstart.ks file will have
user --name admin --plaintext --password "redhat" --gecos "Administrator account"
You can now login to the VM created using the blueprint.
Allowing images created via composer api server to be further customized using cloud-init would be a good thing.
Is there any documentation in this regard ?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2019:3333