Bug 1991843
| Summary: | "filename" DHCP option for anaconda 'inst.ks' not working anymore | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Radek Vykydal <rvykydal> |
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | medium | Docs Contact: | Sagar Dubewar <sdubewar> |
| Priority: | unspecified | ||
| Version: | 9.0 | CC: | acardace, anaconda-maint-list, bgalvani, dcbw, extras-qa, fge, jikortus, jkonecny, jonathan, jstodola, kellin, lkundrak, mclasen, mkolman, release-test-team-automation, rstrode, rvykydal, sdubewar, thaller, thiebolt, vanmeeuwen+fedora, vponcova, vslavik, wwoods |
| Target Milestone: | beta | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | anaconda-34.25.2.2-1.el9 | Doc Type: | Bug Fix |
| Doc Text: |
.Using the `filename` DHCP option no longer blocks downloading the `kickstart` file for installation
Previously, when building a path for getting the kickstart file from an NFS server, the installer did not consider the `filename` DHCP option. As a consequence, the installer did not download the kickstart file and was blocking the installation process. With this update, the `filename` DHCP option correctly constructs a path to the kickstart file. As a result, the kickstart file is downloaded properly, and the installation process starts correctly.
|
Story Points: | --- |
| Clone Of: | 1991516 | Environment: | |
| Last Closed: | 2023-05-09 07:35:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1991823 | ||
| Bug Blocks: | |||
|
Comment 2
Jiri Konecny
2022-04-06 09:58:39 UTC
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 (anaconda 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:2223 |