|
|
Subject: Re: rh80 anaconda crash on failure to map package to filename - msg#00176
List: linux.redhat.kickstart.general
Why are you "unselecting" sendmail, when it's not in your distribution?
How are you exactly specifying the package list in the %packages
section? Are you specifying by group, or by individual packages?
Did you remove any packages that are in the Core and Base group? If so,
then you will need to modify the comps.xml file.
--brett
On Wed, 2003-02-26 at 16:42, Skahan, Vince wrote:
> In trying to kickstart off of a stripped redhat-80 cdrom, I got the following
> exception from anaconda. Should I enter a bugzilla on this at redhat.com ?
>
> Changes made to a vanilla rh80 cd-1:
> - removed a bunch of unnecessary to me rpms from RedHat/RPMS
> - ran genhdlist against the modified tree to update the hdlist files to
> match
> - burned a custom bootable cdrom from it
> - tried to kickstart from the cd
>
> Before anaconda installs anything, it blows up with the attached traceback.
>
> (hopefully I typed these correctly)
> -------------------------------------------------
> Traceback (most recent call last):
> File "/usr/bin/anaconda", line 694 in ?
> intf.run(id,dispatch,configFileData)
> File "/usr/lib/anaconda/text.py", line 402, in run
> (step,args) = dispatch.currentStep()
> File "/usr/lib/anaconda/dispatch.py", line 251 in currentStep
> self.gotoNext()
> File "/usr/lib/anaconda/dispatch.py", line 150 in gotoNext
> self.moveStep()
> File "/usr/lib/anaconda/dispatch.py", line 215 in moveStep
> rc = apply(func,self.bindArgs(args))
> File "/usr/lib/anaconda/packages.py", line 121, in readPackages
> id.instClass.setGroupSelection(id.comps)
> File "/usr/lib/anaconda/kickstart.py", line 1122 in setGroupSelection
> comps.packages[n].unselect()
> File "/usr/lib/anaconda/comps.py", line 171 in __get_item__
> return self.packages[item]
> KeyError: sendmail
>
> Note the last line mentioning sendmail. The sendmail rpm is the first package
> de-selected in my %packages section and it's "not" present on the modified cd.
>
> What I think is happening is anaconda is looking in hdlist for the
> name/filename
> key/value pair for the packages I've told it to 'not' install sayeth my
> ks.cfg file,
> and it's blowing up on not finding the name to precise filename mapping info
> it expects.
>
> In my ks.cfg file, I set "%packages --ignoredeps", so at worst shouldn't it
> just
> log "can't get the filename" and move on to the next item rather than blowing
> up ?
>
> Lastly, what to do ? Choices appear to be:
>
> - fix anaconda to skip packages it can't get the filename for
> (ugh - fix it with a custom updates.img file or unrolling stage2.img?)
>
> - edit out the rpms I've removed from RPMS in comps.xml
> (could I just mark all the ones I've deleted as 'optional' not
> 'mandatory'?)
>
> - put the blasted RPMS on cd to not have to deal with anaconda bugs
> (would really not to burn rpms I won't use onto the cd)
>
> - any others ?
>
> Thanks for any help...
>
> --
> ---------- Vince.Skahan@xxxxxxxxxx ---------
> Connexion by Boeing - Cabin Network
>
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/kickstart-list
--
Brett Schwarz
brett_schwarz AT yahoo.com
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Re: partitioning
On Wed, 26 Feb 2003, Preston Wade wrote:
> Is it possible to create partitions inside of the pre-install script?
I have done so, piping the necessary commands into fdisk.
>
> What we are trying to do is install a new machine but we would like to use
> the --onpart switch to specify which partitions are where, even if the disk
> is brand new with no partitions.
You can use /proc/partitions to discover what partitions already exist,
or if you prefer, fdisk -l, and the use any shell code you like to
change the disk to the way you want it.
--
Please, reply only to the list.
Next Message by Date:
click to view message preview
Re: ondisk
On Wed, Feb 26, 2003 at 03:43:04PM -0500, Reza Hedayati wrote:
>
> My questions is how can we ask kickstart to automatically pick the first
> drive, regardless of the drive type, but to put all the partitions on the
> same drive.
>
You can do something like this in %pre to create partitioning information,
write it to a file (/tmp/partitions in this example), and then %include that
file in your ks.cfg...
%pre --interpreter /usr/bin/python
# load the modules needed to make this work
import os, sys
sys.path.append('/usr/lib/anaconda')
import isys
# get a sorted list of drives
drives = isys.hardDriveDict().keys()
drives.sort()
# write the include file to /tmp/kspart, drives[0] is the first drive,
# drives[1] is the second, etc. To get the filet to be used, put
# '%include /tmp/partitions' in your kickstart configuration.
f = open("/tmp/partitions", "w")
f.write("part / --size 1500 --ondisk %s\n" % drives[0])
f.write("part /boot --size 1500 --ondisk %s\n" % drives[0])
f.write("part /usr --size 1500 --ondisk %s\n" % drives[0])
f.write("part /var --size 1500 --ondisk %s\n" % drives[0])
f.write("part /home --size 1500 --ondisk %s --grow\n" % drives[0])
f.close()
--
Jason Kohles jkohles@xxxxxxxxxx
Senior Engineer Red Hat Professional Consulting
Previous Message by Thread:
click to view message preview
rh80 anaconda crash on failure to map package to filename
In trying to kickstart off of a stripped redhat-80 cdrom, I got the following
exception from anaconda. Should I enter a bugzilla on this at redhat.com ?
Changes made to a vanilla rh80 cd-1:
- removed a bunch of unnecessary to me rpms from RedHat/RPMS
- ran genhdlist against the modified tree to update the hdlist files to match
- burned a custom bootable cdrom from it
- tried to kickstart from the cd
Before anaconda installs anything, it blows up with the attached traceback.
(hopefully I typed these correctly)
-------------------------------------------------
Traceback (most recent call last):
File "/usr/bin/anaconda", line 694 in ?
intf.run(id,dispatch,configFileData)
File "/usr/lib/anaconda/text.py", line 402, in run
(step,args) = dispatch.currentStep()
File "/usr/lib/anaconda/dispatch.py", line 251 in currentStep
self.gotoNext()
File "/usr/lib/anaconda/dispatch.py", line 150 in gotoNext
self.moveStep()
File "/usr/lib/anaconda/dispatch.py", line 215 in moveStep
rc = apply(func,self.bindArgs(args))
File "/usr/lib/anaconda/packages.py", line 121, in readPackages
id.instClass.setGroupSelection(id.comps)
File "/usr/lib/anaconda/kickstart.py", line 1122 in setGroupSelection
comps.packages[n].unselect()
File "/usr/lib/anaconda/comps.py", line 171 in __get_item__
return self.packages[item]
KeyError: sendmail
Note the last line mentioning sendmail. The sendmail rpm is the first package
de-selected in my %packages section and it's "not" present on the modified cd.
What I think is happening is anaconda is looking in hdlist for the name/filename
key/value pair for the packages I've told it to 'not' install sayeth my ks.cfg
file,
and it's blowing up on not finding the name to precise filename mapping info
it expects.
In my ks.cfg file, I set "%packages --ignoredeps", so at worst shouldn't it just
log "can't get the filename" and move on to the next item rather than blowing
up ?
Lastly, what to do ? Choices appear to be:
- fix anaconda to skip packages it can't get the filename for
(ugh - fix it with a custom updates.img file or unrolling stage2.img?)
- edit out the rpms I've removed from RPMS in comps.xml
(could I just mark all the ones I've deleted as 'optional' not
'mandatory'?)
- put the blasted RPMS on cd to not have to deal with anaconda bugs
(would really not to burn rpms I won't use onto the cd)
- any others ?
Thanks for any help...
--
---------- Vince.Skahan@xxxxxxxxxx ---------
Connexion by Boeing - Cabin Network
Next Message by Thread:
click to view message preview
Re: rh80 anaconda crash on failure to map package to filename
On Wed, Feb 26, 2003 at 04:42:41PM -0800, Skahan, Vince wrote:
> KeyError: sendmail
>
> Note the last line mentioning sendmail. The sendmail rpm is the first package
> de-selected in my %packages section and it's "not" present on the modified cd.
>
It's telling you your configuration mentions a non-existant package, if it
isn't on the CD, don't try to deselect it.
--
Jason Kohles jkohles@xxxxxxxxxx
Senior Engineer Red Hat Professional Consulting
|
|