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:
The livemedia-creator install is to a disk image. In RHEL 7 I was able to mount the install ISO in /mnt/install/repo and use the following kickstart url install method:
url --url="file:///mnt/install/repo"
With the same install method used in RHEL 9, livemedia-creator now throws the following message and exits:
The kickstart must activate networking if the url or nfs install method is used.
Version-Release number of selected component (if applicable):
lorax-34.9.14-1.el9.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Create the file test.ks with just one line:
url --url="file:///mnt/install/repo"
2. Run the following command:
livemedia-creator --no-virt --make-disk --ks=test.ks --image-only --dracut-arg=--no-hostonly --image-name image.tmp
Actual results:
The command fails with the following output:
[root@localhost i95code]# livemedia-creator --no-virt --make-disk --ks=test.ks --image-only --dracut-arg=--no-hostonly --image-name image.tmp
2022-10-04 12:52:13,684: livemedia-creator v34.9.14-1
2022-10-04 12:52:13,684: selinux is Disabled
2022-10-04 12:52:13,737: The kickstart must activate networking if the url or nfs install method is used.
2022-10-04 12:52:13,737: The kickstart must activate networking if the url or nfs install method is used.
Expected results:
2022-10-04 15:45:52,314: livemedia-creator v34.9.14-1
2022-10-04 15:45:52,314: selinux is Disabled
2022-10-04 15:45:52,370: disk_img = /var/tmp/image.tmp
2022-10-05 15:45:52,370: Using disk size of 2MiB
2022-10-05 15:45:52,371: Running anaconda.
and then anaconda will continue to install if there is a valid repo located at /mnt/install/repo
Additional info:lorax-28.14.68-1
This also affects the lorax that is shipped with the current RHEL 8.6 (lorax-28.14.68-1).
I already brought this issue up with the github lorax team and they have the following PR to resolve it: https://github.com/weldr/lorax/pull/1273
Reproduced with lorax-34.9.20-1.el9.
Verified with lorax-34.9.21-1.el9, 'url --url="file://..."' can be used without the network command in the kickstart file.
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-2023:2267