[Spacewalk-list] Spacewalk - Cobbler - Kickstart problem
Wolfgang Kamradek
wolfgang at kamradek.de
Mon Jul 6 20:49:25 UTC 2009
Hi,
I've got the problem with the Spacewalk 0.5.3 created Kickstart files
(cobbler 1.6.6) in /var/lib/rhn/kickstart/wizard on CentOS 5.3:
There are two paths for rhn_rpms withing the kickstart file: /tmp/
rhn_rpms and /tmp/rhn_rpms/optional. For me it seems like the
kickstart script first
installs the /tmp/rhn_rpms/optional/* rpms, which causes an error when
it tries to install rhnlib withing /tmp/rhn_rpms, because it's
installed already from tmp/rhn_rpms/optional.
For this reason some rpms are missing and this prevents to
automatically register the specific client to spacewalk. I tried hard
to find the repository that
holds the script snippets to edit them - and found them in diverse
paths. Unfortunatley none of them has any effect to the kickstart file
that will be created.
My best guess for now is that the paths are hard coded into a .class
file: https://fedorahosted.org/spacewalk/changeset/06b89603b02bc4f2ce0b28f484eb02835dd84c43
Is there a way to change the mechanism Spacewalk creates the kickstart
files? I have to admit that I still not understood the mechanism how
Spacewalk creates the kickstart files and
where it gets the needed info/snippets from...
I learned from the roadmap that full editing feature is planed for 0.6
and the following releases. Should I just wait for a few weeks?
For the moment I can work with it - manually modifying the kickstart
files after creation - but things get complicated when I have some
more clients running and I schedule kickstarts for provisioning
and such.
Any hints what would be best practice in my situation?
Thanks in advance,
Wolfgang.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20090706/4d9e1c26/attachment.htm>
More information about the Spacewalk-list
mailing list