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.
Description of problem:
livemedia-creator fails to create an iso using livemedia.ks template on s390x/aarch64.
livemedia.ks packages sections contains
@^workstation-product-environment
s390x and aarch64 do not have workstation-product-environment, so it should probably be similar to the rhel-livemedia.ks from rhel with something like
@base-x
@fonts
@guest-desktop-agents
@hardware-support
@multimedia
@networkmanager-submodules
@workstation-product
@gnome-desktop
Version-Release number of selected component (if applicable):
lorax-34.9.10-1.el9
How reproducible:
Always
Steps to Reproduce:
1. Prepare a working kickstart using the livemedia.ks provided by lorax
2. livemedia-creator --make-iso --no-virt --iso /path/to/boot.iso --ks ks.cfg --nomacboot
Actual results:
2022-01-29 05:13:36,753: Running in cmdline mode, no interactive debugging allowed.
2022-01-29 05:13:36,753: The exact error message is:
2022-01-29 05:13:36,753:
2022-01-29 05:13:36,753: The group 'workstation-product-environment' does not exist.
2022-01-29 05:13:36,753:
2022-01-29 05:13:36,753: The installer will now terminate.
2022-01-29 05:16:38,018: Error in atexit._run_exitfuncs:
2022-01-29 05:16:38,018: Traceback (most recent call last):
2022-01-29 05:16:38,018: File "/usr/lib/python3.9/site-packages/dasbus/client/handler.py", line 477, in _get_method_reply
2022-01-29 05:16:38,018: return self._handle_method_error(error)
2022-01-29 05:16:38,018: File "/usr/lib/python3.9/site-packages/dasbus/client/handler.py", line 497, in _handle_method_error
2022-01-29 05:16:38,018: raise exception from None
2022-01-29 05:16:38,018: dasbus.error.DBusError: umount of /run/user/0 failed (32)
2022-01-29 05:16:38,019: Running anaconda failed: process '['unshare', '--pid', '--kill-child', '--mount', '--propagation', 'unchanged', 'anaconda', '--kickstart', '/mnt/tests/installation/livemedia-creator/build-images/ks.cfg', '--cmdline', '--dirinstall', '--remotelog', '127.0.0.1:46545']' exited with status 1
2022-01-29 05:16:38,019: Shutting down log processing
2022-01-29 05:16:38,088: Install failed: novirt_install failed
2022-01-29 05:16:38,089: Removing bad disk image
2022-01-29 05:16:38,089: ERROR: Image creation failed: novirt_install failed
2022-01-29 05:16:38,089: Image creation failed: novirt_install failed
Expected results:
Iso successfully created
Verified that it's possible to build images using the provided example files on all architectures.
Tested with lorax-34.9.17-1.el9
Marking as Verified:Tested
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 (lorax bug fix and enhancement update), 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/RHBA-2022:8018