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.
.The `inst.repo` kernel boot parameter now works for a repository on a hard drive that has a non-root path
Previously, the RHEL 8 installation process could not proceed without manual intervention if the `inst.repo=hd:<device>:<path>` kernel boot parameter was pointing to a repository (not an ISO image) on a hard drive, and a non-root (/) path was used. With this update, the installation program can now propagate any `<path>` for a repository located on a hard drive, ensuring the installation proceeds as normal.
Description of problem:
Anaconda fails to use inst.repo=hd:<device>:<path> when path is not /.
Version-Release number of selected component (if applicable):
RHEL-8.0.0-RC-2.0 -> RHEL-8.0.0-20190313.0
anaconda-29.19.0.39-1.el8
How reproducible:
always
Steps to Reproduce:
1. Mount the installation ISO and copy the contents to a partition so that the content is not in the / of that partition.
2. Start another installation with inst.repo=hd:<device>:<path> (e.g. inst.repo=hd:vdb1:/iso-content)
3. Anaconda cannot use the installation source.
Actual results:
Anaconda fails to use inst.repo=hd:<device>:<path> when path is not /.
Expected results:
inst.repo=hd:<device>:<path> when path is not / is usable as an installation source in anaconda.
Additional info:
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/RHBA-2019:3417