Hide Forgot
Description of problem: Anaconda fails to start when using kickstart file. Version-Release number of selected component (if applicable): anaconda-11.2.0.58-1 busybox-anaconda-1.2.2-8.fc7 anaconda-runtime-11.2.0.58-1 How reproducible: always Steps to Reproduce: 1. run anaconda using kadischi. 2. run anaconda from cmd-line. 3. Actual results: anaconda goes into an endless 99% usage loop. Expected results: anaconda to build install tree. Additional info: Not using a kickstart file brings up the gui and package selection as normal which then fails to grab some rpms & Release notes from mirrors. so thats two bugs in one report will separate if requested. Attaching Logs /tmp/anaconda.log more info here: https://www.redhat.com/archives/fedora-livecd-list/2007-May/msg00064.html https://www.redhat.com/archives/fedora-livecd-list/2007-May/msg00062.html
Created attachment 154667 [details] anaconda-fails-with-kickstart-file
Created attachment 154668 [details] kickstart file minimal kickstart file
Created attachment 154671 [details] anaconda not finding release notes & rpms
using this command-line now brings up a successful text install, anaconda --kickstart=/home/dexter/mini-ks-cfg.ks --nompath --nodmraid --rootpath=/tmp/kadischi.oluQuu --method=http://mirror.atrpms.net/fedoracore/development/i386/os
components: anaconda-runtime-11.2.0.63-2 busybox-anaconda-1.2.2-8.fc7 anaconda-11.2.0.63-2
requested by Jams Antill
updated to anaconda.i386 0:11.2.0.66-1 anaconda-runtime.i386 0:11.2.0.66-1 will give it a test this week-end.
Created attachment 158289 [details] kadischi-anaconda-crash
ok basically it failed again with anaconda.i386 0:11.2.0.66-1 but the way it failed raised the question about yum 3.2.1-1 it dies if you peruse the logs reverting yum to 3.1.7-2 confirmed this breakage.
This will be fixed in the next build of anaconda.