Tim Verhoeven | 1 Apr 2009 16:10
Picon

Re: [ANNOUNCE] Cobbler 1.6.2

Hi,

I've just upgraded my Cobbler installation to 1.6.2. I've then tried
importing the just released CentOS 5.3 and I get this error :

- cp /var/www/cobbler/ks_mirror/CentOS-5.3-i386/CentOS/repodata/comps.xml
/var/www/cobbler/ks_mirror/CentOS-5.3-i386/CentOS/base/comps.xml
- processing repo at : /var/www/cobbler/ks_mirror/CentOS-5.3-i386/CentOS
- looks like we've already scanned here:
/var/www/cobbler/ks_mirror/CentOS-5.3-i386/CentOS
---------------- (associating kickstarts)
- found content (breed=redhat) at
/var/www/cobbler/ks_mirror/CentOS-5.3-i386/images/xen

local variable 'datestamp' referenced before assignment
  File "/usr/lib/python2.4/site-packages/cobbler/cobbler.py", line 83, in main
    rc = BootCLI().run(sys.argv)

  File "/usr/lib/python2.4/site-packages/cobbler/cobbler.py", line 61, in run
    return self.loader.run(args)

  File "/usr/lib/python2.4/site-packages/cobbler/commands.py", line 122, in run
    return fn.run()

  File "/usr/lib/python2.4/site-packages/cobbler/modules/cli_misc.py",
line 124, in run
    breed=self.options.breed

  File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 594, in
import_tree
(Continue reading)

Michael DeHaan | 1 Apr 2009 16:22
Picon
Favicon

Re: [ANNOUNCE] Cobbler 1.6.2

Tim Verhoeven wrote:
> Hi,
>
> I've just upgraded my Cobbler installation to 1.6.2. I've then tried
> importing the just released CentOS 5.3 and I get this error :
>
>   

Hi Tim,

This has happened before where folks have tried to import something and 
it is missing the .discinfo file. (Was this a DVD import?). A missing 
discinfo
is the root cause of this bug, but we can patch it to tolerate when this 
file is missing. I'll include this for 1.6.3 when it comes out.

I'd be curious if you have any other problems with 5.3 after importing 
this, as I haven't yet tried the CentOS 5.3 ISOs. Hopefully the 
structure is as
we would suspect -- if not, we'll take care of it.

Thanks!

--Michael

diff --git a/cobbler/action_import.py b/cobbler/action_import.py
index e811c11..eb433da 100644
--- a/cobbler/action_import.py
+++ b/cobbler/action_import.py
 <at>  <at>  -1059,6 +1059,8  <at>  <at>  class RedHatImporter ( BaseImporter ) :
(Continue reading)

Jared Hodge | 1 Apr 2009 16:25
Favicon

RE: Stategery regarding Windows support for mixed environments


> -----Original Message-----
> From: cobbler-bounces <at> lists.fedorahosted.org [mailto:cobbler-
> bounces <at> lists.fedorahosted.org] On Behalf Of Michael DeHaan
> Sent: Wednesday, April 01, 2009 7:59 AM
> To: cobbler mailing list
> Subject: Re: Stategery regarding Windows support for mixed
environments
> 
> 
> > As I mentioned, my company would embrace this about as well as it's
> > embraced Vista (i.e. not at all).
> >
> 
> Hi Jared,
> 
> We want to look into integration with cloning tools, or resurrection
of
> the cloning live image that we had going several months ago for
> physical
> installs.    Being able to have all the software installed "full
stack"
> is important, and the workflow will be smoother to get all the
software
> onto the box
> -- while also straining development time much less and offering
> solutions for all OSes, not just Windows.   (Yes, you could use
> this to image GNU Hurd if you wanted).
> 
> Meanwhile, start that Linux port :)
(Continue reading)

Michael DeHaan | 1 Apr 2009 14:58
Picon
Favicon

Re: Stategery regarding Windows support for mixed environments


> As I mentioned, my company would embrace this about as well as it's
> embraced Vista (i.e. not at all).  
>   

Hi Jared,

We want to look into integration with cloning tools, or resurrection of 
the cloning live image that we had going several months ago for physical
installs.    Being able to have all the software installed "full stack" 
is important, and the workflow will be smoother to get all the software 
onto the box
-- while also straining development time much less and offering 
solutions for all OSes, not just Windows.   (Yes, you could use
this to image GNU Hurd if you wanted).

Meanwhile, start that Linux port :)

--Michael
Tom Brown | 1 Apr 2009 19:32

'type' field

Is there any chance we could get a type field into cobbler - similar to 
the description field? I'd really like to be able to use logic on this 
field to decide on what packages to install.

I could use the description field for this but its a bit free form and 
would be nice to be able to have a small field where we can add this 
info into.

If it were easy to do that would be great but if not then no biggie

thanks
Jeff Schroeder | 1 Apr 2009 19:35
Picon

Re: 'type' field

On Wed, Apr 1, 2009 at 10:32 AM, Tom Brown <tom <at> ng23.net> wrote:
> Is there any chance we could get a type field into cobbler - similar to
> the description field? I'd really like to be able to use logic on this
> field to decide on what packages to install.
>
> I could use the description field for this but its a bit free form and
> would be nice to be able to have a small field where we can add this
> info into.
>
> If it were easy to do that would be great but if not then no biggie

You can use the "mgmt classes" along with the puppet integration to
have puppet do it for you. Granted that assumes you use puppet :(

--

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com
James Cammarata | 1 Apr 2009 19:39
Favicon
Gravatar

Re: 'type' field


On Wed, 01 Apr 2009 18:32:02 +0100, Tom Brown <tom <at> ng23.net> wrote:
> Is there any chance we could get a type field into cobbler - similar to 
> the description field? I'd really like to be able to use logic on this 
> field to decide on what packages to install.
> 
> I could use the description field for this but its a bit free form and 
> would be nice to be able to have a small field where we can add this 
> info into.
> 
> If it were easy to do that would be great but if not then no biggie
> 
> thanks
> _______________________________________________
> cobbler mailing list
> cobbler <at> lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler

This is what ksmeta was designed for, you should use that.

--

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Tom Brown | 1 Apr 2009 19:54

Re: 'type' field


>> Is there any chance we could get a type field into cobbler - similar to 
>> the description field? I'd really like to be able to use logic on this 
>> field to decide on what packages to install.
>>
>> I could use the description field for this but its a bit free form and 
>> would be nice to be able to have a small field where we can add this 
>> info into.
>>
>> If it were easy to do that would be great but if not then no biggie
>>
>> thanks
>> _______________________________________________
>> cobbler mailing list
>> cobbler <at> lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/cobbler
>>     
>
> This is what ksmeta was designed for, you should use that.
>
>   

thanks both - i will look at the options, we are using puppet but only 
starting out so maybe i should invest more time there
Michael DeHaan | 1 Apr 2009 19:58
Picon
Favicon

Re: 'type' field

James Cammarata wrote:
> On Wed, 01 Apr 2009 18:32:02 +0100, Tom Brown <tom <at> ng23.net> wrote:
>   
>> Is there any chance we could get a type field into cobbler - similar to 
>> the description field? I'd really like to be able to use logic on this 
>> field to decide on what packages to install.
>>
>> I could use the description field for this but its a bit free form and 
>> would be nice to be able to have a small field where we can add this 
>> info into.
>>
>> If it were easy to do that would be great but if not then no biggie
>>
>> thanks
>> _______________________________________________
>> cobbler mailing list
>> cobbler <at> lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/cobbler
>>     
>
> This is what ksmeta was designed for, you should use that.
>
>   

James and Jeff are both right.

If you want to hijack the management_classes field for your own uses and 
not use Puppet, that's ok too...

--Michael
(Continue reading)

Christopher Dale | 2 Apr 2009 00:00
Picon
Favicon

Error templating file: /etc/dhcpd.conf

[root <at> inCore ~]# cobbler sync

# *** 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.
#
#
# cannot find 'system' while searching for 'iface.system.netboot_enabled'
#   File "/usr/lib/python2.5/site-packages/cobbler/templar.py", line 115, in render
#     data_out = str(t)
#
#   File "/usr/lib64/python2.5/site-packages/Cheetah/Template.py", line 982, in __str__
#     def __str__(self): return getattr(self, mainMethName)()
#
#   File "cheetah_DynamicallyCompiledCheetahTemplate_1238622594_65_47014.py", line 265, in respond
#

Error templating file: /etc/dhcpd.conf


My dhcpd.template file:

[root <at> inCore ~]# cat /etc/cobbler/dhcp.template
# ******************************************************************
# Cobbler managed dhcpd.conf file
#
# generated from cobbler dhcp.conf template ($date)
# Do NOT make changes to /etc/dhcpd.conf. Instead, make your changes
# in /etc/cobbler/dhcp.template, as /etc/dhcpd.conf will be
# overwritten.
#
# ******************************************************************

ddns-update-style interim;

allow booting;
allow bootp;
#if $omapi_enabled
omapi-port $omapi_port;
#end if

ignore client-updates;
set vendorclass = option vendor-class-identifier;

subnet 192.168.10.0 netmask 255.255.255.0 {
     option subnet-mask         255.255.255.0;
     range dynamic-bootp        192.168.10.100 192.168.10.254;
     filename                   "/pxelinux.0";
     default-lease-time         21600;
     max-lease-time             43200;
     next-server                $next_server;
}

subnet 192.168.56.0 netmask 255.255.255.0 {
     option subnet-mask         255.255.255.0;
     range dynamic-bootp        192.168.56.100 192.168.56.254;
     filename                   "/pxelinux.0";
     default-lease-time         21600;
     max-lease-time             43200;
     next-server                $next_server;
}

subnet 192.168.122.0 netmask 255.255.255.0 {
     option subnet-mask         255.255.255.0;
     range dynamic-bootp        192.168.122.100 192.168.122.254;
     filename                   "/pxelinux.0";
     default-lease-time         21600;
     max-lease-time             43200;
     next-server                $next_server;
}

#for dhcp_tag in $dhcp_tags.keys():
    ## group could be subnet if your dhcp tags line up with your subnets
    ## or really any valid dhcpd.conf construct ... if you only use the
    ## default dhcp tag in cobbler, the group block can be deleted for a
    ## flat configuration
# group for Cobbler DHCP tag: $dhcp_tag
group {
        #for mac in $dhcp_tags[$dhcp_tag].keys():
            #set iface = $dhcp_tags[$dhcp_tag][$mac]
    host $iface.name {
        hardware ethernet $mac;
        #if $iface.ip_address:
            fixed-address $iface.ip_address;
        #end if
        #if $iface.subnet:
            option subnet-mask $iface.subnet;
        #end if
        #if $iface.gateway:
            option routers $iface.gateway;
        #end if
        #if $iface.system.netboot_enabled:
            filename "$iface.filename";
            ## Cobbler defaults to $next_server, but some users
            ## like to use $iface.system.server for proxied setups
            next-server $next_server;
            ## next-server $iface.system.server;
        #end if
    }
        #end for
}
#end for


_______________________________________________
cobbler mailing list
cobbler <at> lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Gmane