June 2009 - cobbler - Fedora Mailing-Lists

cobbler buildiso / livecd with static ip

by Simon Woolsgrove

With koan there is the ability to supply --static-interface to configure the boot line for static ip build but using buildiso it will default to eth0 or bond with eth0. If I specify ksdevice=mac or ksdevice=eth1 as a kernel param, buildiso passes ksdevice=xxx but takes the ip details from eth0, which if I passed ksdevice=eth1 would be the wrong ip details. Is is worth amending the code to pay attention to ksdevice or say allowing a new parameter in the network config to pass say --bootif=[mac|ethx] and then getting buildiso to use that ? I am happy to take a look at the code but not sure of best direction ? Other thoughts with koan livecd would there be a away to detect the correct interface for a given ip ? We have servers that have multiple cards and dependant on hardware, version of linux working out the correct eth becomes a real headache. Even knowing MAC addresses does not always allow you to plug the correct cable into the right port. Cheers, Simon

14 years, 10 months

1
0
0 / 0

Unicode bug on RHEL5 (ex: "adding repo - oddity" thread)

by L B

Hello, Even after an upgrade to Cobbler 1.6.6 on RHEL5, I still had the unicode bug adding "u" in front of profiles,repos etc... I fixed this problem by upgrading python-simplejson to version 2.0.5 replacing EPEL RPM by rpmforge RPM (instead of 2.0.3). Package here : http://packages.sw.be/python-simplejson/ and then rpm -Uvh Hope it helps, -- L.B.

14 years, 10 months

3
5
0 / 0

Non-linux installation

by Jared Hodge

All, Forgive me if this has been addressed recently, I haven't been monitoring the mailing list very closely. A few months ago there was quite a bit of discussion about support for windows XP (via ris-linux) and other non-linux operating systems (via cloning). I believe the decision was made to favor support of cloning over other options. Has any progress been made on this front? I was going to suggest looking at including "g4l" (ghost for linux - http://sourceforge.net/projects/g4l/) as the cloning option. It seems that this would be very easy to get working since it supports ftp access to the images and already has a bootable linux image for the cloning tool itself. I would think all that would be needed is an option to load this bootable image though the current pxe/bootiso options and possibly add some lipstick to have a clean method of selecting the image to be used or created on the cobbler server. Anyway, maybe this discussion has moved to the development mailing list, but I was just hoping for an update. Thanks. -Jared

14 years, 10 months

4
20
0 / 0

can't boot domU built from koan

by C R

Hi, After getting set straight about the '-xen' distro's I can use 'cobbler buildiso' to install all the server types I need (including dom0's... thanks goes to Michael) now the problem is using 'koan' to build domU's... I have confirmed that my profiles for the domU's are using the '-xen' distro's and confirmed that the 'system' configurations are using the correct profiles..... here's the problem.... the domU install works flawlessly using 'koan --server=[server] --virt --system=[system]'... disk-0 is created the correct size and the kickstart works (including %post).... I confirmed that the correct 'initrd.img' and 'vmlinuz' are retrived from the cobbler server... the install can be monitored thru 'virt-manager'.... '/etc/xen/[server]' is created with the correct data.... the domU is halted as per the kickstart.... starting the new domU from 'virt-manager' fails.... also 'xm list' only shows the dom0... the interface, static IP, name servers, netmask are all translated variables in the kickstart.... what am I missing? any help is appreciated..... from '/var/log/xend.log'....... XendError: Error creating domain: (2, 'invalid kernel', 'xc_dom_find_loader: no loader found\n') profile beign used...... cobbler report --name=domU-rhel4 profile : domU-rhel4 distro : rhel4.8-xen-i386 comment : virtual server created : Thu May 21 15:31:20 2009 dhcp_tag : default enable_menu : True kernel options : {} mgmt_classes : [] modified : Wed Jun 17 10:55:06 2009 name servers : [] name servers search : [] owners : admin post kernel options : {} redhat mgmt key : <<inherit>> redhat mgmt server : <<inherit>> repos : [] server : <<inherit>> template_files : {} virt bridge : xenbr0 virt cpus : 14 virt file size : 32 virt path : /var/lib/xen/images virt ram : 4096 virt type : xenpv

14 years, 10 months

2
1
0 / 0

Network config snippet...

by Vic

Hi All. I've almost got my first PXE cobbler installation going. But I'm stumped... My kickstart file ins=cludes the network_config snippet. In that, there is the line: %include /tmp/pre_install_network_config Now I'm not sure whether this file is suppsed to be included on the cobbler server & passed down in-line (in which case why /tmp?), or whether it's supposed to be downloaded separately by the target - if so, that doesn't seem to be happening :-( Can anyone show me what I've done wrong? I'm using 1.6.5 on a RHEL4-alike server, in case that's relevant. Thanks! Vic.

14 years, 10 months

3
2
0 / 0

Cobbler - Kickstarts

by Brown, Scott D CTR, E2

So this is what I get for breaking the #1 sysadmin rule - If it's not broken don't fix it!..... I decided to upgrade my cobbler from 0.9 to 1.4.1 (yeah I know) and ran into a huge problem... During my cobbler import of my RHEL 5.1, 5.2 DVD's I came across this error when trying to add my custom kickstart to the profile... Cobbler import -- path=/mnt/rhel51_iso/ --name=DISA_RHEL51_Client_i386 --kickstart=/root/disa.ks Error: Kickstart file can only be specified when a specific breed is selected This is the last piece of the puzzle for me as I need this kickstart as part of my IA lockdown build. Any help would be appreciated. Thanks.. V/R Scott Brown NAVAIR PMA-231 SIAP IA/SysAdmin CompTIA Security+ CompTIA Linux+

14 years, 10 months

3
3
0 / 0

Ldaps authentication

by jaj＠teamlog.com

Hello, I try to authenticate my users with ldap on cobbler (1.6.2-1.el5). It's ok if I use following parameters : ldap_server: "ldap.example.com" ldap_base_dn: "ou=people,dc=example,dc=com" ldap_port: 389 ldap_tls: 1 ldap_anonymous_bind: 1 ldap_search_bind_dn: '' ldap_search_passwd: '' ldap_search_prefix: 'uid=' On the ldap server side I have : slapd[12978]: conn=98188 fd=45 ACCEPT from IP=172.24.113.35:58129 (IP=0.0.0.0:389) slapd[12978]: conn=98188 op=0 STARTTLS slapd[12978]: conn=98188 op=0 RESULT oid= err=0 text= slapd[12978]: conn=98188 fd=45 TLS established tls_ssf=256 ssf=256 But it's not working when I use ldaps. With following parameters : ldap_server: "ldap.example.com" ldap_base_dn: "ou=people,dc=example,dc=com" ldap_port: 636 ldap_tls: 1 ldap_anonymous_bind: 1 ldap_search_bind_dn: '' ldap_search_passwd: '' ldap_search_prefix: 'uid=' The demo_connect python script raises this error : # python /tmp/demo_connect.py --user=USER - trying to login with user=USER Traceback (most recent call last): File "/tmp/demo_connect.py", line 37, in ? token = sp.login(options.user,options.password) File "/usr/lib64/python2.4/xmlrpclib.py", line 1096, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.4/xmlrpclib.py", line 1383, in __request verbose=self.__verbose File "/usr/lib64/python2.4/xmlrpclib.py", line 1147, in request return self._parse_response(h.getfile(), sock) File "/usr/lib64/python2.4/xmlrpclib.py", line 1286, in _parse_response return u.close() File "/usr/lib64/python2.4/xmlrpclib.py", line 744, in close raise Fault(**self._stack[0]) xmlrpclib.Fault: <Fault 1: 'exceptions.IOError:[Errno 9] Bad file descriptor'> And with following parameters : ldap_server: "ldap.example.com" ldap_base_dn: "ou=people,dc=example,dc=com" ldap_port: 636 ldap_tls: 0 ldap_anonymous_bind: 1 ldap_search_bind_dn: '' ldap_search_passwd: '' ldap_search_prefix: 'uid=' I obtain this error : # python /tmp/demo_connect.py --user=USER - trying to login with user=USER Traceback (most recent call last): File "/tmp/demo_connect.py", line 37, in ? token = sp.login(options.user,options.password) File "/usr/lib64/python2.4/xmlrpclib.py", line 1096, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.4/xmlrpclib.py", line 1383, in __request verbose=self.__verbose File "/usr/lib64/python2.4/xmlrpclib.py", line 1147, in request return self._parse_response(h.getfile(), sock) File "/usr/lib64/python2.4/xmlrpclib.py", line 1286, in _parse_response return u.close() File "/usr/lib64/python2.4/xmlrpclib.py", line 744, in close raise Fault(**self._stack[0]) xmlrpclib.Fault: <Fault 1: 'ldap.SERVER_DOWN:{\'desc\': "Can\'t contact LDAP server"}'> On the ldap server side I have : slapd[12978]: conn=98193 fd=45 ACCEPT from IP=172.24.113.35:40328 (IP=0.0.0.0:636) slapd[12978]: conn=98193 fd=45 closed (TLS negotiation failure) I read on the mailing list that somebody had a similar problem on Active Directory but I haven't found the solution. Thanks for your help.

14 years, 10 months

2
1
0 / 0

Any natty tools for adding to initrd?

by Vic

Hi All. I want to add a network driver to the initrd of a distro I'm not actually running anywhere. Is there a slappy feature hidden somewhere in the cobbler tool to do this, or have I got to build it by hand? Thanks! Vic.

14 years, 10 months

4
6
0 / 0

Using cobbler for a PPC Install

by Mackell, Thomas O

I would like to install a Linux machine on a Pseries lpar. Would this actually work like the regular linux installs? Or is there a bunch of hoops to jump through, to get this to work. BTW, Going to try Redhat 5.3 for the install, if it makes any difference. Thomas Mackell

14 years, 10 months

2
1
0 / 0

A minor buguette in the RPM...

by Vic

Hi All. PXE seems to be working nicely now (thanks, everyone!). One thing I did pick up on, though - the RPM doesn't seem to create the directory /var/log/cobbler/anamon . Without this, there's a traceback dump all over the newly-installed box... HTH Vic.

14 years, 10 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

cobbler June 2009