Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: nomodeset inst.ks=hd:sdd1:/ks.cfg root=live:LABEL=F18TEST kernel: 3.6.10-4.fc18.i686 package: anaconda-18.37.3 product: Fedora release: Cannot get release name. type: libreport version: 18-TC3
Created attachment 665397 [details] File: anaconda-tb
Created attachment 665398 [details] File: anaconda.log
Created attachment 665400 [details] File: ifcfg.log
Created attachment 665402 [details] File: ks.cfg
Created attachment 665404 [details] File: syslog
Started this installation from USB with vmlinuz, initrd.img and squashfs.img on the USB together with the kickstartfile. Installed on a network segment where there is no DHCP present. So the host can not determine network parameters from the network. In the kickstartfile there is a network configuration present. Anaconda dropped me in in the network configuration screen, but did not take over the network data as defined in the kickstart file. I regard this irrational. If anaconda can't find network information from the network and this information is present in the kickstart file, why not use it. While I was typing the network addresses the system crashed because it could not find the repository. Anaconda does not give me enough time to fill in network addresses. My consideration: First anaconda should not crash at this point. Because this crash does not give the user an opporunity to make a repository accessible. Second there is no reason for anaconda not to find a repository anyway, because the kickstart file supplies all data necesary to configure anaconda and find the repository.
I think that your kickstart network configuration was not applied because you are not specifying --device in network command. We used to support this before loader -> dracut transition.
Your case might be even more specific in that you are fetching kickstart from storage, not over network, although I am not sure if for the latter omitting --device in network actually works.
(In reply to comment #7) > I think that your kickstart network configuration was not applied because > you are not specifying --device in network command. We used to support this > before loader -> dracut transition. Leaves the question: should or shouldn't it be supported in the dracut universe. To be able to use kickstart files in a more generic sense, I think we have to support the use without --device specified. Especially because with the new naming conventions for network devices, it is hard to predict how the device will be called. eth0 was easiers to guess ;-)
(In reply to comment #8) > Your case might be even more specific in that you are fetching kickstart > from storage, not over network, although I am not sure if for the latter > omitting --device in network actually works. That is exactly where the shoe does not fit. In the scenario where the kickstart file is fetched over the network there is no use/ it is impossible to configure the network device with information from the kickstart file, and this is obvious. But when making the kickstart file available before the network has to be configured, as I do, you have the opportunity to use kickstart data to configure it. As the info is there we should not let anaconda crash. IMHO this is in line with user experience. The user has provided the information, why doesn't anaconda use it. It is not a good idea to have a crash, when from the user point of view, there is no need to.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.