-
Bug
-
Resolution: Won't Do
-
Normal
-
rhel-9.7
-
No
-
Moderate
-
rhel-anaconda
-
None
-
False
-
False
-
-
No
-
None
-
None
-
None
-
Unspecified Release Note Type - Unknown
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
When a RHEL-9.7.0-20250521.6 installation is started with several inst.ks= options together with inst.ks.all, Anaconda only fetches the last kickstart. This would be a valid behaviour without the inst.ks.all option, however with this option, Anaconda should try to fetch all of the kickstarts sequentially and use the first successfully fetched one.
Example with inst.ks.all rd.info inst.ks=http://srv/ks/default9 inst.ks=http://srv/ks/default9-invalid inst.ks=http://srv/ks/default9-2 on kernel command line:
# journalctl | grep default9 Jun 06 08:34:18 localhost kernel: Command line: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=RHEL-9-7-0-BaseOS-x86_64 inst.ks.all rd.info inst.ks=http://srv/ks/default9 inst.ks=http://srv/ks/default9-invalid inst.ks=http://srv/ks/default9-2 Jun 06 08:34:18 localhost kernel: Kernel command line: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=RHEL-9-7-0-BaseOS-x86_64 inst.ks.all rd.info inst.ks=http://srv/ks/default9 inst.ks=http://srv/ks/default9-invalid inst.ks=http://srv/ks/default9-2 Jun 06 08:34:19 localhost dracut-cmdline[317]: Using kernel command line parameters: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=RHEL-9-7-0-BaseOS-x86_64 inst.ks.all rd.info inst.ks=http://srv/ks/default9 inst.ks=http://srv/ks/default9-invalid inst.ks=http://srv/ks/default9-2 Jun 06 08:35:51 localhost.localdomain dracut-initqueue[1213]: anaconda: kickstart locations are: http://srv/ks/default9-2 Jun 06 08:35:51 localhost.localdomain dracut-initqueue[1213]: anaconda: fetching kickstart from http://srv/ks/default9-2 Jun 06 08:35:51 localhost.localdomain dracut-initqueue[1213]: anaconda: successfully fetched kickstart from http://srv/ks/default9-2 Jun 06 08:35:51 localhost.localdomain dracut-initqueue[1213]: anaconda: kickstart locations are: http://srv/ks/default9-2 Jun 06 08:35:51 localhost.localdomain dracut-initqueue[1213]: anaconda: fetching kickstart from http://srv/ks/default9-2 Jun 06 08:35:51 localhost.localdomain dracut-initqueue[1213]: anaconda: successfully fetched kickstart from http://srv/ks/default9-2
What is the impact of this issue to you?
Reliability of starting a kickstart installation may be affected as the redundancy to fetch the kickstart from several possible places is missing, potentially requiring manual intervention.
Please provide the package NVR for which the bug is seen:
anaconda-34.25.5.17-1.el9_6
How reproducible is this bug?:
Always.
Steps to reproduce
- Prepare several kickstarts available via HTTP.
- Start the installation with inst.ks.all inst.ks=http://server/testks1 inst.ks=http://server/testks2 inst.ks=http://server/testks3 rd.info on kernel command line.
- In the installation environment, inspect the logs, e. g.:
journalctl | grep testks
Expected results
The first available kickstart is fetched and used for installation.
Actual results
The last kickstart specified on kernel command line is fetched and used for installation.
Additional notes
RHEL-9.6.0-20250222.8 / anaconda-34.25.5.16-1.el9 works as expected.
