disabling second nic and HP firmware cd...
by Corey Kovacs
Folks,
Is there a built in 'correct' way to ensure that my second nics are
not configured during build and left alone when using the network
config snippets delivered with cobbler?
RIght now, when the nodes finish building, the undefined second nic
tries to dhcp even though I've not given it a config.
I am getting around this by making the appropriate changes to
ifcfg-eth1 via two 'sed' lines but if there is a 'better' way I'd
rather do that than rely on a post config.
Also,
are people using the livecd boot method for booting HP firmware disks?
How about the SSTK?
Thanks
Corey
13 years, 4 months
F14 beta python-cheetah regression
by Chad Huneycutt
I am relaying this to the list in case anyone else gets bitten. I
can't take any credit for the solution; heffer on #cobbler had already
worked through this.
In my case, the symptom was that when I tried to generate kickstarts,
if there were any $SNIPPET macros in the kickstart template, I would
see the following behaviour:
[root@yoda-1 Cheetah]# cobbler system getks --name=jedi000
# *** ERROR ***
#
# There is a templating error preventing this file from rendering correctly.
#
# This is most likely not due to a bug in Cobbler and is something you can fix.
#
# Look at the message below to see what things are causing problems.
#
# (1) Does the template file reference a $variable that is not defined?
# (2) is there a formatting error in a Cheetah directive?
# (3) Should dollar signs ($) be escaped that are not being escaped?
#
# Try fixing the problem and then investigate to see if this message goes
# away or changes.
#
#
# SNIPPET() takes exactly 2 arguments (1 given)
# File "/usr/lib/python2.7/site-packages/cobbler/templar.py", line
121, in render
# data_out = t.respond()
#
# File "cheetah_DynamicallyCompiledCheetahTemplate_1288193687_92_18157.py",
line 258, in respond
#
# File "cheetah_DynamicallyCompiledCheetahTemplate_1288193687_92_18157.py",
line 84, in __errorCatcher3
#
# File "<string>", line 1, in <module>
#
heffer tracked it down to this Cheetah commit:
http://github.com/rtyler/cheetah/commit/43d7cbe361a3fe73dc20337e544144b8c...
If you remove the lines added by that commit, then things work better.
I don't pretend to understand this problem beyond that, though, so
either cobbler or cheetah may need to be further modified to
differently attack the problem that commit was addressing.
--
Chad M. Huneycutt
13 years, 5 months
partitioning
by Gavin Reid
Hi All , I am having problems with disk partitioning a section from my kickstart file follows
#get the number of hard disks and there names
set $(list-harddrives)
let numd=$#/2
drive1=$1
drive2=$3
# Default data and rootvg size
swapsize=8192
pv2size=1
pv1size=8196
if [ $numd = 1]; then # only one disk
cat <<=EOpart > /tmp/part-include
part /boot --fstype ext3 --size=100 --ondisk=$d1 --asprimary
part pv.100 --size $pv1size --ondisk=$d1 --asprimary
part pv.200 --size $pv2size --grow --ondisk=$d1 --asprimary
volgroup rootvg pv.100
volgroup datavg pv.200
logvol / --fstype ext3 --vgname=rootvg --size=8196 --name=rootvol
logvol /tmp --fstype ext3 --vgname=rootvg --size=548 --name=tmpvol
logvol swap --fstype swap --vgname=rootvg --size=$swapsize --name=swapvol
logvol /data --fstype ext3 --vgname datavg --size 1 --grow --name=nobackup
EOpart
else
cat <<=EOpart > /tmp/part-include
part /boot --fstype ext3 --size=100 --ondisk=$d1 --asprimary
part pv.100 --size $pv1size --ondisk=$d1 --asprimary
part pv.200 --size $pv2size --grow --ondisk=$d2 --asprimary
part pv.300 --size 1 --grow --ondisk$d1 --asprimary
volgroup rootvg pv.100
volgroup datavg pv.200 pv.300
logvol / --fstype ext3 --vgname=rootvg --size=8196 --name=rootvol
logvol /tmp --fstype ext3 --vgname=rootvg --size=548 --name=tmpvol
logvol swap --fstype swap --vgname=rootvg --size=$swapsize --name=swapvol
logvol /data --fstype ext3 --vgname datavg --size 1 --grow --name=nobackup
EOpart
fi
%include /tmp/part-include
yet the installer explodes at the include line ... it seem that the /tmp/part-include is not created ... any ideas or better methods of partitioning
13 years, 6 months
Problems providing RHEL6 by Cobbler
by Thorben.Erichsen@kba.de
Hello,
i am trying to add RHEL6 to Cobbler (2.0.3.1). I started using --> cobbler import --name=RHEL6 --path=/rhel6-dvd
The importprocess completed successfully so that i was going on to install the first rhel6-system.
Within the installprocess the installations stops with the following Error:
"Unable to read package metadata......
Cannot retrieve repository metadata (repomd.xml)...."
By switching the console (ALT+F3) i found the reason for this error.
Anaconda is searching the repomd.xml in a wrong directory (http://123.456.789.10/cblr/links/RHEL6-64-x86_64/repodata/repomd.xml), which was not created by cobbler import and is also not at the original DVD-ISO.
Is there a solution for this case or what am i doing wrong?
Thanks in advance and best regards
Thorben
13 years, 6 months
Installing ESXi with Cobbler
by Paul Maunders
Hi all,
I notice there has been some discussion on the cobbler-devel mailing list
about using Cobbler to install ESXi 4.1.
I'm interested in testing this, but I'm a bit of a novice when it comes to
using Cobbler, so would anyone be willing to give me an overview of the
steps involved in getting this setup? We do have an existing cobbler
installation, but we are using it in a production environment so initially I
would like to test on a standalone cobbler install.
Others may find this helpful too, so perhaps a page could be added to the
Cobbler Wiki docs?
Regards,
Paul Maunders
13 years, 6 months
Cobbler Puppet External Nodes Classifier
by Thomas A. McGonagle
> Hello,
> When I visit the URL http://cobbler/cblr/svc/op/puppet/hostname/lrzend01
> I receive:
> classes: []
> parameters: {}
> I have tried both fqdn and short-names. I have tried specifying both in the "Hostname" parameter in the GUI and on the CLI.
>
> I am unable to get cobbler to return the mgmt classes that I am specifying at the System and Profile levels. Its as if cobbler can't find these hosts. I am running cobbler versions:
>
> cobbler-2.0.3.1-3.el5
> cobbler-web-2.0.3.1-3.el5
>
> I have double checked the config files and haven't found a misconfiguration.
>
> Any help with this issue would be greatly appreciated. Thanks a lot!
> -Tom
>
>
13 years, 6 months
.ks template for a KVM host
by Dick Davies
Does anyone have a sample .ks template to setup a KVM host
ready for 'koan'ing guests onto?
Mainly I think it just needs the kvm kmod, koan and virt-install
added to the base packages (which is a doddle) but ideally
also the bridge configuration (which I have no idea how to do;
if it wasn't for the upcoming rhel-6 dropping xen support I'd stick
with that just to avoid having to mess around with it).
13 years, 6 months
Interesting issue
by Norman Weathers
Hello,
We recently started using cobbler and Spacewalk together, and have run into an
interesting issue. The way Spacewalk and cobbler work together create
interesting path names under /tftpboot for the images that it needs to boot
from during installation.
Example:
/tftpboot/images/centos-55-x86_64:1:SpacewalkDefaultOrganization is one of our
default install locations. Now, we had been able to do some small scale
installs, but yesterday decided to go big (let's say some where over several
hundred nodes). These nodes have dual interfaces, so we carefully put them
into cobbler (cobbler system add --name.....). Once we were done, nothing can
install now. It seems that tftp has an issue all of the sudden with the
colons in the path, deciding that the colons are service/host names, not path
names. This whole thing had been working until we started to add those
several hundred or more nodes.
I have run cobbler sync several times, restarted cobblerd, and no errors seem
to be reported anywhere.
Here is the output from cobbler sync where it is doing the copying/hardlinks
for the tftpboot/images directrories:
copying bootloaders
copying distros
copying files for distro: centos-55-x86_64:1:SpacewalkDefaultOrganization
copying: /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/vmlinuz -> /tftpboot/images/centos-55-x86_64:1:
SpacewalkDefaultOrganization/vmlinuz
copying: /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/initrd.img -> /tftpboot/images/centos-55-x86_64
:1:SpacewalkDefaultOrganization/initrd.img
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/vmlinuz -> /var/www/cobbler/images/centos-55-
x86_64:1:SpacewalkDefaultOrganization/vmlinuz
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/initrd.img -> /var/www/cobbler/images/centos-55-
x86_64:1:SpacewalkDefaultOrganization/initrd.img
copying files for distro: centos-55-x86_64xen:1:SpacewalkDefaultOrganization
copying: /var/satellite/distro-trees/CentOS-5.5-x86_64/os/images/xen/vmlinuz -
> /tftpboot/images/centos-55-x86_64xen:1:SpacewalkDefaultOrganization/vmlinuz
copying: /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/initrd.img -> /tftpboot/images/centos-55-
x86_64xen:1:SpacewalkDefaultOrganization/initrd.img
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/vmlinuz -> /var/www/cobbler/images/centos-55-
x86_64xen:1:SpacewalkDefaultOrganization/vmlinuz
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/initrd.img -> /var/www/cobbler/images/centos-55-
x86_64xen:1:SpacewalkDefaultOrganization/initrd.img
copying files for distro: Centos-5_5-x86_64:1:SpacewalkPublicCert
copying: /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/vmlinuz -> /tftpboot/images/Centos-5_5-
x86_64:1:SpacewalkPublicCert/vmlinuz
copying: /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/initrd.img -> /tftpboot/images/Centos-5_5-
x86_64:1:SpacewalkPublicCert/initrd.img
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/vmlinuz -> /var/www/cobbler/images/Centos-5_5-
x86_64:1:SpacewalkPublicCert/vmlinuz
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/initrd.img -> /var/www/cobbler/images/Centos-5_5-
x86_64:1:SpacewalkPublicCert/initrd.img
copying files for distro: Centos-5_5-x86_64xen:1:SpacewalkPublicCert
copying: /var/satellite/distro-trees/CentOS-5.5-x86_64/os/images/xen/vmlinuz -
> /tftpboot/images/Centos-5_5-x86_64xen:1:SpacewalkPublicCert/vmlinuz
copying: /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/initrd.img -> /tftpboot/images/Centos-5_5-
x86_64xen:1:SpacewalkPublicCert/initrd.img
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/vmlinuz -> /var/www/cobbler/images/Centos-5_5-
x86_64xen:1:SpacewalkPublicCert/vmlinuz
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/initrd.img -> /var/www/cobbler/images/Centos-5_5-
x86_64xen:1:SpacewalkPublicCert/initrd.img
copying images
generating PXE configuration files
Has anyone seen anything like this, or is there some limitation or change that
is needed to be made in a config script some where? Any direction would be
appreciated.
Norman Weathers
13 years, 6 months
First cobbler check on a new server
by drew einhorn
Before cobbler check would run at all I had to
start cobblerd
start httpd
sudo /usr/sbin/setsebool -P httpd_can_network_connect=1
Now tells me about lots of things that need to be fixed,
but I'm stuck on the first one:
1 : you need to set some SELinux content rules to ensure cobbler serves
content correctly in your SELinux environment, run the following:
/usr/sbin/semanage fcontext -a -t public_content_t "/tftpboot/.*" &&
/usr/sbin/semanage fcontext -a -t public_content_t
"/var/www/cobbler/images/.*"
# usr/sbin/semanage fcontext -a -t public_content_t "/tftpboot/.*"
/usr/sbin/semanage: File context for /tftpboot/.* already defined
Tried changing add to modify
# /usr/sbin/semanage fcontext -m -t public_content_t "/tftpboot/.*"
/usr/sbin/semanage: File context for /tftpboot/.* is not defined
That didn't help. Let's try a delete, then an add.
# /usr/sbin/semanage fcontext -d -t public_content_t "/tftpboot/.*"
/usr/sbin/semanage: File context for /tftpboot/.* is defined in policy,
cannot be deleted
Hmm. Looks like redhat has changed the default selinux configuration in a
way that's incompatible with the cobbler install instructions. I'll bet
somebody here will come up with the right incantation, before I manage to
read and understand the selinux documentation I've been promising myself
that I'll get around to studying someday.
--
Drew Einhorn
"You can see a lot by just looking."
-- Yogi Berra
13 years, 6 months
understanding inherit
by Arnau Bria
Hi all,
first of all: I'm new to cobbler.
I've read the abundant doc (most of them) and now I have my
distro, my profile and my system which has been correctly reisntalled.
Now I'm playing with inheritance, and, if I've understood it correctly,
goes from profile to system. But if I modify kickstart at sytem
level, profile's kisckstart is not used, and that gives a lot of freedom
to systems' kisckstart and the people who will be able to create them.
So, I'd like to allow systems to add some code to kickstart, but not
all, I mean, to inherit profile part (root passwd, puppet
integration, ....).
So my question is: may I configure cobbler to automatically add some
part of code to a system kickstart because it belongs to a profile
meanwhile I give some freedom (partitioning, i.e) to system kickstart?
Many thanks in advance,
Arnau
13 years, 6 months