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
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
wget hangs syncing CentOS repos
by Andy Miller
Folks,
I've set up a Cobbler server to mirror CentOS 5.4. Everything seems OK,
except that when I do a reposync things hang.
Having a poke arround seems to indicate that reposync is trying to wget
comps.xml from the repos, but the CentOS repos don't have a comps.xml.
If I kill the wget, then the rest of the reposync seems to procede OK,
but this is kind of stops the reposync being an overnight task.
Any ideas how I can cure this?
Many Thanks
Andy Miller
--
The Miller Family
doneath(a)fmail.co.uk
14 years, 1 month
Different networks during and after installation
by Luc de Louw
Hi there,
I got cobbler up and running, work perfect. After going to a more
production ready setup I detected some problems.
What I want to is the following:
1. Having the cobbler server in a separate install network
2. Getting an temporary IP from cobblers, DHCP
3. System installation by PXE
4. Register to a RHN Satellite
5. yum -y update
6. Configuring production Network with static IP
7. Power down the system
8. Unplug install network cable and plug in production network cable
I changed the DHCP template to disable IP reservation successfully, so
up to step 3 all went fine. For tests with Centos I skip step 4 for the
moment.
It seems that the pre_install_network_config snippet is configuring the
network too early away from the DHCP settings which ends up in no
network connectivity causing yum update failing.
Any idea how to change the snippets and/or ks template to get the above
steps done?
Thanks,
Luc
14 years, 2 months
Cobbler default system not working
by James Labocki
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?
-James
14 years, 2 months
#errorCatcher Echo no longer works with kickstart templates
by Justin Sherrill
The handy macro (#errorCatcher Echo) used to work with cobbler and it's
templated kickstarts. We could juts include that at the top of a
kickstart file, and whenever a variable ($foo) was encountered, if a
variable by that name wasn't set it would simply echo that out. So
instead of throwing an error, $foo would be printed. This no longer
works correctly and any time it is included, you will get the following
error:
#
# ErrorCatcher instance has no attribute 'listErrors'
# File "/usr/lib/python2.4/site-packages/cobbler/templar.py", line
122, in render
# self.last_errors = t.errorCatcher().listErrors()
#
Any ideas?
Thanks
--
Justin Sherrill, RHCA 1801 Varsity Drive.
Software Engineer Raleigh, NC 27603
Red Hat, Inc.
14 years, 2 months
Re: post_install_network_config snippet
by Jeff Schroeder
On Thu, Jan 21, 2010 at 6:41 AM, Jonathan Sabo <jsabo(a)criminal.org> wrote:
> Has anyone else or could anyone else who uses this snippet try and render a
> kickstart and see if it's still working with the git master please? I'm
> going nuts trying to figure out if it's me or something that's changed that
> is preventing it from rendering. I just see the
> $SNIPPET('post_install_network_config') displayed and it's not in a #raw
> either.... This was working awhile ago but since I started checking again
> recently it's not. If someone could check it out it would be a big help.
Perhaps the remote kickstart support that was recently merged broke
it? If we keep having problems with that code it should be reverted.
--
Jeff Schroeder
Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com
14 years, 2 months
Site specific settings
by Glenn Bailey
What's the best method to define site specific settings? I basically have multiple Cobbler servers setup at various physical locations and each of these locations have different DNS, NTP, Timezones, etc. For DNS it appears I could use the "name_servers" option in the settings file, but that would be the only one.
At first I thought I could maintain a separate snippet to define the options for each location, but I do a full sync off of my master server would overwrite the said file. I want to try and keep from touching the kickstart on each server anytime I do an update on the master server. Perhaps something in cheetah_macros? This file is blank so I don't have an example to use here, or even knowledge of what is capable with it.
I can do this via scripting, just thought there may be an easier way to just "define" them so to speak ;-)
glenn - terremark
14 years, 2 months
Getting rid of bad cobbler metavariables
by Adam Rosenwald
A FAQ that I have brought up on numerous occasions on IRC involves
'getting rid of bad cobbler metavariables'.
If I were to set a wrong ks_meta variable NAME, how do I get rid of the
NAME without taking out ks_meta entirely.
E.g.
`cobbler system add --name=NAME --ksmeta='arg0=val0 arg1=val1
*art2*=val2 ... argN=valN' ...`
There are quite a number of scenarios where I don't want to remove all
of ksmeta, but only a mistyped variable name. I have heard about the
'!ARG' syntax:
E.g.
`cobbler system edit --in-place --name=NAME --ksmeta='*!art2*'`
Supposedly this syntax will, upon deserialization of the JSON, clear the
ks_meta namespace of *art2*; however, upon issuing a report on a given
entity, the flawed variable will still appear along with the negated
variable.
I.e.
ks_meta : 'arg0=val0 arg1=val1 *art2*=*val2* ... argN=valN *!art2*'
For those who make use of this data for inventory or other purposes, the
'!VAR' notation does not cut it. I would like a definitive explanation
of how to remove bad metavariables irrespective of deserialization.
Thanks,
- A.
14 years, 2 months
Buildiso options
by Hagberg, Keith
I am new to using cobbler features and have been wondering if the following is possible.
I have built a kickstart profile inside my satellite. I would like to build a boot iso using cobbler buildiso and have it copy the kickstart file into the iso file and append the cmdline to point at the kickstart file. I also would like it to default the boot to that kickstart, not the local disk.
Thanks
Keith
14 years, 2 months