Cobbler 1.6.3 and Genome
by Alex Wood
Greetings,
I'm using the Genome project ( http://fedorahosted.org/genome ) to
manage a set of VMs. Genome uses Cobbler's XMPRPC API to create a
profile for a system before using Koan to create the system.
Recently I upgraded to Cobbler 1.6.3. Afterwards, machines that were
Koan'ed were unable to download their kickstart files. It turns out
that the Cobbler system profile for those machines did not have a
network interface configured. Previously, in Cobbler 1.1.1, an
interface was configured by default.
Is there anyway to edit a profile such that all systems descended from
it will have a network interface already configured? Otherwise, the
alternative is me having to patch the XMLRPC calls in Genome to create
the interface when the system is created.
------------------
Regards,
Alex Wood
--
Software Engineer
Red Hat
919.754.4445
15 years
Re: preserve pxelinux.cfg ?
by Tom Brown
Tom Brown wrote:
> Jeff Schroeder wrote:
>
>> On Wed, May 6, 2009 at 10:16 AM, Tom Brown <tom(a)ng23.net> wrote:
>>
>>
>>> Is it possible to have cobbler not blat pxelinux.cfg but merely add to
>>> it or delete from it?
>>>
>>> We have a situation where the same build box is needed to PXE different
>>> systems, jumpstart etc, but i dont want to not be able to use cobbler.
>>> Anything that gets added into there not by cobbler gets removed when a
>>> sync is run.
>>>
>>> Any ideas on if this could work?
>>>
>>>
>> The pxelinux.cfg is generated from a template. I believe it is
>> /etc/cobbler/pxe/pxedefault.template. You should be able to add what
>> you want to the template and have it generate the file. You could also
>> use host specific pxe config files for the solaris boxes or whatnot.
>>
>>
>>
>
> moved to user list at Michael's request
>
> I see that pxedefault.cfg contains
>
> DEFAULT menu
> PROMPT 0
> MENU TITLE Cobbler | http://cobbler.et.redhat.com
> TIMEOUT 200
> TOTALTIMEOUT 6000
> ONTIMEOUT local
>
> LABEL local
> MENU LABEL (local)
> MENU DEFAULT
> LOCALBOOT 0
>
> $pxe_menu_items
>
> MENU end
>
> That is the pxe menu configuration isn't it ? Its possible i am getting
> confused but what i need to happen is that files within
> /tftpboot/pxelinux.cfg/ are not removed if cobbler does not know about
> them. If thats possible by using that template could you give any tips
> as what to put in there?
>
>
sorry - OK really sent to user list now
15 years
bug in manage_isc.py
by Gareth Armstrong
Hello Folks,
first off a big thanks for this very fine piece of software that is
cobbler. I am currently playing with it as part of an investigation for
my team and it impresses me more and more. That said, I think I may
have a bug for you.
In summary dhcpd chokes after a cobbler sync when you add a system with
a full domain name using the "--hostname" option of cobbler system add.
This is because "option host-name" in dhcpd only takes the machine name.
Below is a transcript of the commands used to illustrate the bug and a
patch that corrects the behavior.
Many thanks in-advance,
Gareth
cobbler system add --name=donkey11 --mac=XX:XX:XX:XX:XX:XX --ip=1.2.3.4 \
--hostname=donkey11.somewhere.com \
--dns-name=donkey11.somewhere.com --profile=hocoe-rhel5.3-i386
--dhcp-tag=subnet2
cobbler sync
/usr/sbin/dhcpd -t failed
cobbler trigger failed: cobbler.modules.sync_post_restart_services
May 6 22:15:25 repoman dhcpd: Internet Systems Consortium DHCP Server
V3.0.5-RedHat
May 6 22:15:25 repoman dhcpd: Copyright 2004-2006 Internet Systems
Consortium.
May 6 22:15:25 repoman dhcpd: All rights reserved.
May 6 22:15:25 repoman dhcpd: For info, please visit
http://www.isc.org/sw/dhcp/
May 6 22:16:18 repoman dhcpd: Internet Systems Consortium DHCP Server
V3.0.5-RedHat
May 6 22:16:18 repoman dhcpd: Copyright 2004-2006 Internet Systems
Consortium.
May 6 22:16:18 repoman dhcpd: All rights reserved.
May 6 22:16:18 repoman dhcpd: For info, please visit
http://www.isc.org/sw/dhcp/
May 6 22:18:38 repoman dhcpd: /etc/dhcpd.conf line 66: semicolon expected.
May 6 22:18:38 repoman dhcpd: option host-name donkey11.
May 6 22:18:38 repoman dhcpd: ^
May 6 22:18:38 repoman dhcpd: Configuration file errors encountered --
exiting
May 6 22:18:38 repoman dhcpd:
May 6 22:18:38 repoman dhcpd: If you did not get this software from
ftp.isc.org <ftp://ftp.isc.org>, please
May 6 22:18:38 repoman dhcpd: get the latest from ftp.isc.org
<ftp://ftp.isc.org> and install that before
May 6 22:18:38 repoman dhcpd: requesting help.
May 6 22:18:38 repoman dhcpd:
May 6 22:18:38 repoman dhcpd: If you did get this software from
ftp.isc.org <ftp://ftp.isc.org> and have not
May 6 22:18:38 repoman dhcpd: yet read the README, please read it
before requesting help.
May 6 22:18:38 repoman dhcpd: If you intend to request help from the
dhcp-server(a)isc.org <mailto:dhcp-server@isc.org>
May 6 22:18:38 repoman dhcpd: mailing list, please read the section on
the README about
May 6 22:18:38 repoman dhcpd: submitting bug reports and requests for help.
May 6 22:18:38 repoman dhcpd:
May 6 22:18:38 repoman dhcpd: Please do not under any circumstances
send requests for
May 6 22:18:38 repoman dhcpd: help directly to the authors of this
software - please
May 6 22:18:38 repoman dhcpd: send them to the appropriate mailing list
as described in
May 6 22:18:38 repoman dhcpd: the README file.
May 6 22:18:38 repoman dhcpd:
May 6 22:18:38 repoman dhcpd: exiting.
cobbler system remove --name=donkey11
cobbler system add --name=donkey11 --mac=XX:XX:XX:XX:XX:XX --ip=1.2.3.4 \
--hostname=donkey11 \
--dns-name=donkey11.somewhere.com --profile=hocoe-rhel5.3-i386
--dhcp-tag=subnet2
cobbler sync
Shutting down dhcpd: [ OK ]
Starting dhcpd: [ OK ]
[root@repoman modules]# hg qdiff
diff -r 00e6c2050399 manage_isc.py
--- a/manage_isc.py Wed May 06 23:03:47 2009 +0200
+++ b/manage_isc.py Wed May 06 23:06:17 2009 +0200
@@ -230,7 +230,7 @@
interface["next_server"] = blended_system["server"]
interface["netboot_enabled"] =
blended_system["netboot_enabled"]
- interface["hostname"] = blended_system["hostname"]
+ interface["hostname"] =
blended_system["hostname"].split('.')[0]
interface["filename"] = "/pxelinux.0"
# can't use pxelinux.0 anymore
cobbler system remove --name=donkey11
cobbler system add --name=donkey11 --mac=XX:XX:XX:XX:XX:XX --ip=1.2.3.4 \
--hostname=donkey11.somewhere.com \
--dns-name=donkey11.somewhere.com --profile=hocoe-rhel5.3-i386
--dhcp-tag=subnet2
cobbler sync
Shutting down dhcpd: [ OK ]
Starting dhcpd: [ OK ]
--
15 years
Problems with network bonding and RHEL4
by James Cammarata
Ok, so I've been doing some research after trying to use cobbler to build a
few systems with bonding for the first time. I noticed that it puts the
bonding options in the ifcfg file rather than modprobe.conf, and understand
that's the "proper" way to do things, but my research shows that was
something that was added to RHEL5 (and presumably probably started post
Fedora 8/9).
Is this method supported in RHEL4 though? We built these systems using
RHEL4.6 and bonding is as follows:
$ grep BONDING_OPTS /etc/sysconfig/network-scripts/ifcfg-bond0
BONDING_OPTS="mode=1 miimon=100 primary=eth1"
$ cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v2.6.3-rh (June 8, 2005)
Bonding Mode: load balancing (round-robin)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth1
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:22:19:2b:0b:18
Slave Interface: eth2
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:1b:21:34:16:00
So it's defaulting to RR, when it should be doing A/S. Am I doing
something wrong, or is this method not supported on RHEL4? When setting up
bonding previously, I've only ever put the options in modprobe.conf.
Thoughts?
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
15 years
PXE Menus and Cobbler
by Matt Ford
Hi All,
I have a cobbler installation: two distros (centos 4 and centos 5) and
couple of profiles.
I'm not using dns or dhcp management.
Cobbler check and cobbler sync both run okay.
I'm expecting that the profiles created should automagically be added to the
PXE boot menu I'm using. But they are not? Am I wrong to expect this
behaviour? How else might I list my profiles in the PXE boot menus? I can
only see any fresh distro I import....
If it should be happening what should I check for?
I did try adding a system but this didn't help either.....
Thanks for any pointers,
Matt Ford.
15 years
[IMPORTANT] command line rename can delete sub objects (like profiles under distros, etc), patch attached
by Michael DeHaan
The problem Smooge reported with cobblerd yesterday evening deals with
cobblerd doing some undesirable things when rename commands are made in
the CLI.
AFAIK, this is a 1.6.3 bug but may be present in earlier versions.
This will be included in 1.6.4, out Thursday or Friday, but is included
here for completeness.
Users should, without question, apply this patch, if they use the CLI
and will ever use, intentionally or otherwise, the "rename" command:
*http://tinyurl.com/crkgkx
*
There may be some further fixing to the logic behind this for 1.6.4,
though we've confirmed this takes care of the problem.
--Michael
15 years
Ouch I lost all my systems.
by Stephen John Smoogen
Well I was doing some house cleaning today.. in trying to add red hat
distro 5.3 to the cobbler box etc. I did what I normally do
cobbler import --breed=redhat --arch=i386 --mirror=/mnt/iso/
--name=rhel-5.3-server-i386
geta list of 5.2 systems and move them to 5.3
for i in cain1_unm_edu cain2_unm_edu cellini_unm_edu crux_unm_edu
docbook-new_unm_edu enyo_unm_edu eprint_new_unm_edu megrez_unm_edu
pallas_unm_edu quasi_unm_edu scheat_unm_edu sedna_unm_edu
thrymr_unm_edu varuna_unm_edu vm-banana-t_unm_edu vortigern_unm_edu
zimbra2_unm_edu; do cobbler system edit --name=$i
--profile=rhel-5.3-server-i386; done
cobbler list shows them pointing to the right profile.
I am running out of space and need to update others so I did a
cobbler profile remove --name=rhel-5.2-server-i386
cobbler distro remove --name=rhel-5.2-server-i386
and Pow.. no more systems when I do a cobbler systems list.. Not sure
where they went or why they went away.. the directory
/var/lib/cobbler/config/systems.d/ is empty.
What did I do wrong?
--
Stephen J Smoogen. -- BSD/GNU/Linux
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"
15 years
cobbler-ext-nodes - no output
by Léon Keijser
Hi,
I'm trying to set up external nodes to integrate puppet into cobbler. On
one cobbler server my colleague (Jasper) already set things up right and
i get a valid output:
# /usr/bin/cobbler-ext-nodes first.host.name
classes: [base, func, koan, stonerepo, nrpe, logrotate, audit,
rhcs-cloud, gvrp, xen-sysctl]
parameters: {from_cobbler: 1, tree:
'http://@@http_server@@/cblr/links/RHEL-5.3-x86_64'}
On the one i'm setting up there's no output however:
# /usr/bin/cobbler-ext-nodes other.host.name
classes: []
parameters: {}
The 'other.host.name' exists though. It's profile has the
management_classes set in the same way as 'first.host.name' has.
Cobbler's settings file (excerpt) looks like this:
mgmt_classes: [base-virtual, func, stonerepo, nrpe, logrotate, audit]
mgmt_parameters:
from_cobbler: 1
Kind regards,
--
Léon
15 years
"... is broken" / or: how to ask about bugs
by Michael DeHaan
Random mailing list tip.
The statement "feature X is broken" doesn't help me much as I don't know
what that means. Worse, it means I have to try it to figure out if I
can figure out what may
or may not be broken, and that takes up a fair amount of time.
Broken can mean something throws a traceback, doesn't work like you
think it should, or perhaps something quite different.
So, when posting problems, it helps if everyone can please include the
following:
(A) What command or operation you were trying to run. If this was on
the command line, include the actual command or commands from your bash
history.
(B) What you expected to happen or where trying to do
(C) What actually happened. If this was on the command line, include
the full output of the command and other commands as relevant, like
sections of "cobbler report"
(D) If there is an exception, include the tails of /var/log/cobbler
(for local operations) or /var/log/cobblerd (for web operations) to show
those exceptions. This can be skipped
if it's obvious, such as the exception is already visible from the
command line, or there is no exception and the behavior is just
different than expected.
Most folks are pretty good about this, but in general, it's better to
have more detail than less. This goes not just for cobbler, but all
projects ...
Thanks!
--Michael
15 years
Cobbler starting its managed services
by Fabien Dupont
Hi.
Another question today (I might be kind of brain heating today).
As far as I know, Cobbler generates config files and restart/reload the
services it manages (DHCP/DNS for instance) when syncing.
Why wouldn't it start them at boot time if they are managed ? Admins
would'nt have to mind about those services anymore, as cobbler would do it
for them.
--
Fabien
15 years
