yum upgrade to 1.2.6-1.el5
by Harry Hoffman
Just upgraded to the latest cobbler from epel-testing... the
post-install script fails :-(
Updating : cobbler ####################### [ 5/10]
profile CentOS-5.2-x86_64 not found, inheritance not possible
Stopping cobbler daemon: [ OK ]
Starting cobbler daemon: Traceback (most recent call last):
File "/usr/bin/cobblerd", line 32, in ?
api = bootapi.BootAPI()
File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 90, in
__init__
self.deserialize()
File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 448, in
deserialize
return self._config.deserialize()
File "/usr/lib/python2.4/site-packages/cobbler/config.py", line 186,
in deserialize
serializer.deserialize(self._profiles)
File "/usr/lib/python2.4/site-packages/cobbler/serializer.py", line
125, in deserialize
rc = storage_module.deserialize(obj,topological)
File
"/usr/lib/python2.4/site-packages/cobbler/modules/serializer_yaml.py",
line 136, in deserialize
obj.from_datastruct(datastruct)
File "/usr/lib/python2.4/site-packages/cobbler/collection.py", line
144, in from_datastruct
item = self.factory_produce(self.config,seed_data)
File
"/usr/lib/python2.4/site-packages/cobbler/collection_profiles.py", line
41, in factory_produce
return profile.Profile(config).from_datastruct(seed_data)
File "/usr/lib/python2.4/site-packages/cobbler/item_profile.py", line
87, in from_datastruct
self.set_parent(self.parent)
File "/usr/lib/python2.4/site-packages/cobbler/item_profile.py", line
131, in set_parent
raise CX(_("profile %s not found, inheritance not possible") %
parent_name)
cobbler.cexceptions.CX: 'profile CentOS-5.2-x86_64 not found,
inheritance not possible'
[FAILED]
error: %post(cobbler-1.2.6-1.el5.noarch) scriptlet failed, exit status 1
Any ideas?
Cheers,
Harry
14 years, 8 months
$tree in kickstart
by Tom Brown
Is this now depricated in 1.6 ??
+------+ Kickstart Error
+-------+
|
|
| Unknown Url method $tree
|
|
|
| +----+
|
| | OK |
|
| +----+
|
|
|
|
|
+--------------------------------+
and the template looks like
# Use network installation
url --url=$tree
thanks
14 years, 11 months
post_install_network_config oddity
by Gennadiy Nerubayev
This particular snippet is giving me issues in that it's apparently not
templating at all. All other snippets are working fine. The rendered
kickstart for a system that was only created with a name, still contains:
$SNIPPET('post_install_network_config')
If I look at the rendered view for the profile, it returns the following, as
it should:
# Start post_install_network_config generated code
# End post_install_network_config generated code
This is regardless if I use my custom kickstart template or sample.ks, on
v1.4.2. There are no apparent errors in the logs - is there anything I can
do to debug this further?
Thanks,
-Gennadiy
15 years, 1 month
Re: [PATCH] keep_ssh_host_keys and logging-snippets
by Jasper Capel
On Thu, 2009-03-12 at 17:03 +0000, Tom Brown wrote:
> >> dont suppose you could forward me the ssh snippet could you as i could
> >> do with testing it and i cant seem to get git going at the moment
> >>
> >> thanks
> >>
> >
> > Sure, there you go!
> >
> >
>
>
> sorry to follow this up directly with you but do you know why this might
> occur
> *snip*
> it only happens when i try to use the ssh snippet and its when the pre
> snippets get run - any clue how i can do about debugging this?
>
> thanks
(And on-list again, please use the list for issues like this, others can
learn from it, or help)
Hmm. No, I'll run a few tests of my own sometime next week.
Unfortunately, debugging %pre is a pain. You actually can't, in
text-only mode, as you can't swap out to the console / logs using ALT
+f2 / ALT+f3. You'll have to use virt-manager to get to those screens, I
guess. Maybe someone has a better idea.
If you add that log_ks_pre snippet I just posted to the top of the %pre
section, you might have some useful information during that stage
under /tmp.
Did this happen for you using the old one as well? (I'd guess so, as the
error doesn't indicate LVM).
-Jasper
15 years, 1 month
Stategery regarding Windows support for mixed environments
by Michael DeHaan
This is a development branch thing but it's related to Cobbler's plan
moving forward, so it seems best to discuss here.
So ... there's been some good work going so far towards supporting some
variants of Windows, though I see it may perhaps be somewhat of an
evolutionary dead-end.
The web page for RIS-Linux in particular does not mention Vista or
2008. Further, I am much more interested in supporting Windows virtually
than physically -- this should be natural with the increasing interest
in virtualization and recent interoperability agreements with Microsoft.
For the devel branch (1.7), I'd rather we refocus our efforts into
making sure the experience for Windows installs, virtually, is as good
as possible.
The upside of this is that most of the infrastructure is already in
place -- we can already do ISO based fullvirt installs ("cobbler image
add" with the ISO file
residing on NFS) and a next step is to teach it about a virtual floppy
drive with the SIF answer file on the drive, so it can be fully scripted.
We already also have the "virt-clone" image type, for being able to take
an existing disk image and repeatedly clone that image with koan,
keeping the same
source image on NFS. (The syntax here is "koan --image=foo --virt",
just like with the ISO based installs for virt).
The goal here is to not invest too much effort in supporting dead-end
deployment areas and writing code to cater to say, XP vs Vista vs 2003
vs 2008, but handle
things generically, with answer files, and images, things we already
do. On the plus side, there's also much less work in doing this and
no additional dependencies
or things to configure and set up.
Rather than physical deployments this encourages deploying Windows on
Linux hosts, which makes the Windows machines easier to manage since you
can run
tools like libvirt and Func on the hosts. See
http://www.redhat.com/promo/svvp/
Windows belongs running on virt. In general, for non-Linux OS's, we
should also concentrate on virt.
--Michael
15 years, 1 month
http proxy setting for repo to mirror locally
by Leonid Flaks
Hi !
I would like to provision rpmfusion repos in cobbler. I can access them
only through the web proxy. Is it supported in cobbler? What would be
the right place to put the proxy setting for those repos?
The proxy support has been added recently to anaconda during manual
installation, but I could not find any way to put it in kickstart, so
just adding 'repo= ' does not work. I found that anaconda uses
/tmp/anaconda-yum.conf (or so it seems) for yum configuration and tried
to put proxy settings there in pre script - did not have any effect.
Another thing I tried - to mirror it locally - then 'cobbler reposync'
would need to be configured to use proxy.
For now I just use post install - configure yum and run 'yum install'
in scripts.
I am using cobbler 1.4.3-4 on fedora 10, repo is set as http://
Thanks,
Leon
15 years, 1 month
