Red Hat Bugzilla – Bug 77875
Choosing Minimal packages breaks anaconda
Last modified: 2007-04-18 12:48:27 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021106
Description of problem:
If I include only Minimal packages in ks.cfg anaconda bails out with a Python
Steps to Reproduce:
Include only this in your ks.cfg
Installation will fail. I may have even included packages such as DHCP and
similar thing happened :-(.
Could you actually attach the traceback you receive? I do minimal kickstarts
all the time without problems
[ Network boot with bootnet.img, ks.cfg on floppy. ]
The output of the Kickstart Configurator reads as
when selecting "Minimal" in the packages selection. Anaconda doesn't know about
that and returns a key error "Minimal" in line 580 of comps.py. I tried "@Base"
and it worked.
Minimal isn't a package group found in the comps file.
Yes, so the problem is with the graphical kickstart configurator here ...
Shouldn't this be reassigned to ksconfig component then ?
Time tracking values updated