Cobbler 2.0.1 Triggers?
by Jonas Hagberg
Hej.
My old trigger don't work any more. None of my test triggers are
executed either.
I have them in
/var/lib/cobbler/triggers/install/post
How are you supposed to write triggers these days?
I am using s shorter variant of the cfenginge ppkeys trigger found on.
https://fedorahosted.org/cobbler/wiki/CobblerTriggers
I have the cfengine on the same server as cobbler. But it dont work any
more.
I have also tried to copy and edit a trigger in the.
site-packages/cobbler/modules
i used the install_post_log.py as template
But id don't seam to run either.
Any one could tell me how to do it the right way?
cheers
--
-------------------------------------------
Systemexpert jonas.hagberg(a)it.uu.se
Jonas Hagberg tel 018 - 471 1026
UPPMAX fax: 018 - 51 19 25
Uppsala universitet
Box 337, Lägerhyddsv 2E, Hus 4, room 4111
751 05 Uppsala www.uppmax.uu.se
-------------------------------------------
14 years, 1 month
Re: Cobbler default system not working
by James Labocki
Scott,
Thanks for the reply. Can you expand upon:
"Cobbler doesn't really map to pxe in the standard way. The cobbler
system name isn't exposed to pxe in the way that you are assuming."
Also, per the man page of cobbler in the "SYSTEM" section:
===
name
The system name works like the name option for other commands.
If the name looks like a MAC address or an IP, the name will implicitly be used for either --mac
or --ip of the first interface, respectively. However, it’s usually better to give a
descriptive name -- don’t rely on this behavior.
A system created with name "default" has special semantics. If a default system object exists,
it sets all undefined systems to PXE to a specific profile. Without a "default" system name
created, PXE will fall through to local boot for unconfigured systems.
When using "default" name, don’t specify any other arguments than --profile ... they won’t be
used.
===
To me that says that if I use --name=default all undefined machines should use that profile. Am I misinterpreting the man page? Also, I don't want to modify the PXE directory directly because if `cobbler sync` is ever run in the future then the contents will be overwritten.
-James
----- Original Message -----
From: "Scott Henson" <shenson(a)redhat.com>
To: "cobbler" <cobbler(a)lists.fedorahosted.org>
Sent: Friday, January 29, 2010 3:06:20 PM GMT -05:00 US/Canada Eastern
Subject: Re: Cobbler default system not working
Excerpts from James Labocki's message of Fri Jan 29 14:46:45 -0500 2010:
> Using cobbler-1.6.6-3.el5sat
>
> After setting up a default system in cobbler using `cobbler system add --name=default --profile=rhel5mrg`
>
> systems continue to boot to localdisk instead of using the rhel5mrg profile
>
> # cobbler list
> distro ks-rhel-x86_64-server-5
> distro ks-rhel-x86_64-server-5-u1
> distro ks-rhel-x86_64-server-5-u1:xen
> distro ks-rhel-x86_64-server-5-u2
> distro ks-rhel-x86_64-server-5-u2:xen
> distro ks-rhel-x86_64-server-5-u3
> distro ks-rhel-x86_64-server-5-u3:xen
> distro ks-rhel-x86_64-server-5-u4
> profile coe-mrg-grid:1:Red-Hat
> profile coeiadrhel5base:1:Red-Hat
> distro ks-rhel-x86_64-server-5-u4:xen
> distro ks-rhel-x86_64-server-5:xen
> distro rhel54server64
> profile rhel5mrg
> system 00:1A:4A:0F:45:16
> system default
>
> When I use `cobbler system add --name=default --profile=rhel5mrg --mac=00:1A:4A:0F:45:16` the system then boots to rhel5mrg. What am I missing?
Cobbler doesn't really map to pxe in the standard way. The cobbler
system name isn't exposed to pxe in the way that you are assuming.
The pxe system is keyed off off the mac address only. You can put a
default directly in pxe (in the normal way) pointing at the rhel54mrg
profile. This will make systems boot by default into the mrg profile.
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
14 years, 1 month
How about declaring a network interface but not enabling at install ?
by Fabien Dupont
Hi all.
Do you think it would be useful to have a 'configure at install' boolean
field for network interfaces ? This field would
tell post_install_network_config snippet if an interface is meant to be
configured by Cobbler. As I see it, it would allow me to provision a network
interface with is configured by other means.
My need is to declare two interfaces with the same MAC adress but configured
on different networks, a Windows and a Linux dedicated one. The DHCP
configuration would manage both interfaces with 'dhcp_tag' field and a
template meant for this, and only one interface would be configured by
Linux.
The changes in post_install_network_config would be small (an if condition).
What do you think of this idea ?
--
Fabien
14 years, 1 month
Cobbler CentOS 5.4 x86_64 unattended Install issue
by Adurotec
I have been using cobbler 1.6.6 for my vmware esxi 4.0 CentOS 5.4 i386
installs with no problem. I imported the i386 5.4 DVD and created a
kickstart template for all of the servers I have setup.
Now I am trying to do the same thing for the 64 bit version of CentOS
5.4 within a vmware guest, the install makes it to the boot menu, but
once I make a choice and proceed with the install I get prompted for the
TCP/IP configuration. Once I put that information in the install
proceeds unattended.
It looks like the DHCP assignment for the installer is failing, but I am
not sure where to check to verify that is indeed the problem or if it is
something else.
Could someone help point me in the right direction.
Thanks,
David
14 years, 1 month
Dependency problem installing Cobbler 1.6.6 on CentOS 5.4
by Marcelo Garcia
Hi
I'm trying to set up a Cobbler server on a CentOS 5.4 (x86_64) machine.
When I run "cobbler check", I got the following message:
#0: yum-utils need to be at least version 1.1.17 for reposync -l,
current version is 1.1.16
I image the same problem should happens with RHEL, is this right? Is
there a workaround for this?
Thanks
Marcelo.
14 years, 1 month
gpxe and cobbler
by Larry Brigman
Is anyone using gpxe instead of pxelinux with cobbler?
I have a case that loop mounted ISO's are available via http.
I also have a NFS path to these mount points but the data doesn't show up except
the first loop mount.
The case here is I build new ISO's for our testing every day and
pulling those over
to the cobbler server is extra work and storage space.
14 years, 1 month
bind management
by James Wilcoxson
Hi, I setup Cobbler for the first time this week and ran into a problem
with the bind management feature. My bind instance is in a chroot jail
which works fine with the named template however doesn't quite work with the
zone template. Cobbler places the forward/reverse zone files in
'/var/named/' within manage_bind.py. I think a bind_chroot flag and
bind_chroot_path would be good additions to the settings file and provide a
straight forward way to accommodate this bind configuration. I'm currently
working around this by adding the below symlinks, which correspond to to my
forward and reverse zone names in /etc/cobbler/settings.
lrwxrwxrwx 1 root root 38 Feb 19 06:51 foo.com ->
/var/named/chroot/var/named/foo.com
lrwxrwxrwx 1 root root 37 Feb 19 06:51 192.168.2 ->
/var/named/chroot/var/named/192.168.2
As I mentioned, this is my first time using Cobbler. Let me know if I'm
misunderstanding something.
Thanks.
-Joe Wilcoxson
14 years, 2 months
RFE #260
by Zubin Mithra
Hello,
I have been looking at the tickets at the cobbler trac. I came across
this one and find this one interesting to work on.
Ticket 260
https://fedorahosted.org/cobbler/ticket/260
The feature to be added is a provision for easy manipulation of the
kickstart password in the ".ks" files. I have been through the mailing
lists and find the following solution for the problem.
https://fedorahosted.org/pipermail/cobbler/2008-October/001198.html
So, my understanding of the implementation is as follows:-
1.
---------------------------------------------------------
cobbler passwd --template=path
cobbler passwd --all
cobbler passwd --stock-templates-only
----------------------------------------------------------
In the first line the template refers to a configuration file for
certain types of kickstart files. If the kickstart filename matches a
particular pattern, then the kickstart password is modified to the
value corresponding to the pattern in the template.
The second and the third lines are unclear to me.
I am not sure if my idea is correct; if not please help clear it up.
Thanking you,
Zubin Mithra
14 years, 2 months
Cobbler replicate over different "server" ip
by Glenn Bailey
Howdy,
I'm getting the following error when I try to do a replicate:
Exception occured: xmlrpclib.ProtocolError
Exception value: <ProtocolError for mia21654bcu001.managed.cln/cobbler_api: 502 Bad Gateway>
My hunch this is because the IP I'm trying to replicate from is our "front side" management network, and
the IP I have set in the "server" section of cobbler is our "back side" non-routable build network. Anyone
have a setup like this or know of a way around it?
Glenn E. Bailey III, Configuration Services
gbailey(a)terremark.com
469-461-9126
terremark worldwide
222 W Las Colinas Blvd Ste 350E
Irving, TX 75039
14 years, 2 months