can cobbler create new subnets on dhcpd.conf on its own?
by Christian Horn
Hi,
cobbler takes dhcp.template and creates /etc/dhcpd.conf with it
just fine.
There has to be a subnet-entry thou for each network segment the
deployed servers are coming up from. Until now we manually edit
dhcp.template for this.
Isnt all required data for this already in the 'cobbler system'
object? Cobbler could check if the subnet we want to boot from
is already in the dhcp.template or create such an entry in the
final dhcpd.conf .
Maybe its already doing this but i am missing the peaces?
Christian
14 years, 5 months
Cobbler and func filetracker
by Harry Hoffman
Hi,
I seem to remember someone talking about setting up filetracking via
func at install time.
I can't remember if it's built into cobbler or if someone was just using
snippets.
Anyone know?
Cheers,
Harry
14 years, 5 months
push based replication
by Jon Sabo
Does anyone out there replicate cobbler in a push rather than pull
fashion? Imagine you have a master server that pushes to slaves who
are unable to connect back to the master server. How do you go about
doing that?
Thanks,
Jonathan
14 years, 5 months
Difference between installing Centos 5.3 from DVD and with Cobbler?
by Mykel Alvis
Hi All,
I have an odd problem on VMware ESX Server 2.5.3 build-35703, and was
wondering if anyone else had this issue.
I have created a new VM with 1G of ram and 8G of disk space, using the
LSILogic SCSI controller with virtual bus sharing.
When I import the Centos 5.3 i386 DVD iso into Cobbler and do an PXE install
with that imported distro, the system installs (with one slight problem) and
then reboots. When it reboots after installation, it gets to a point where
the remote console tells me :
...
mptbase: ioc0: Initiating bringup
ioc0: LIS53C1030 B0: Capabilities={Initiator}
and then there's a popup dialog that says the following:
VMware ESX Server unrecoverable error: (vcpu-0)
NOT_IMPLEMENTED F(5411):3237
Please request support and include the contents of the log file:
"/root/vmware/linux/vmware.log". We will respond on the basis of your
support entitlement.
When I look in the aforementioned file, it tells me something that seems
important:
Nov 11 16:51:19: vcpu-0| LSILogic: Adapter 0 Port 0 Operational.
Nov 11 16:51:19: vcpu-0| LSILogic: LSILogicProcessSDRMessage: Unhandled
Message Function 0x7
Nov 11 16:51:19: vcpu-0| NOT_IMPLEMENTED F(5411):3237
The LSILogic SCSI adapter is the only one that Centos will use from my vast
list of two (vmxlsilogic and vmxbuslogic). The vmxbuslogic doesn't produce
visible partitions when installing so it's not particularly usefule. The
LSILogic install completes, but with the above symptoms after the
post-install reboot.
Now for the weirdish part:
When I mount the iso the Centos 5.3 DVD as a DVD ISO device on the same VM
and install from virtual DVD, the system seems to work rather well. It
installs and reboots and comes up (eventually, after running firstboot) to a
login prompt.
I've spent the last couple of hours searching the interwebs about such
things. I would (and will) send my request to the vmware communities, but
since the disparity seems to be between Cobbler and a regular DVD install, I
figured I'd try here first and see if anyone had similar experiences.
Could this be an issue around the create-repo issue that is supposed to be
solved in Cobbler 2.0? That appears to be the only difference between the
two installs (i.e. the state of the repo at install time).
Any advice would be greatly appreciated.
Mykel
14 years, 5 months
Debugging snippets
by Max Krasnyansky
Folks,
I'm looking for suggestions on how to debug snippet code. I got a
snippet here that fails for some systems but works for others.
When I say fails I mean that it does not get expanded, I just
git this
$SNIPPET('my_snippet')
in the final kickstart.
The interesting thing is that this snippet starts failing after the
system is edited with the web UI. I diffed .json files before and after
and I do not see anything obvious in there (I mean there are differences
but they seem fairly minor). There are no errors in the logs.
So is there any way to enable verbose mode in cheetah or something to
see why the snippet is not getting expanded ?
I'm running F11 box with
$ rpm -q cobbler
cobbler-2.0.1-1.fc11.noarch
Thanx
Max
14 years, 5 months
Re: Support for Fedora 12?
by Scot Floess
Silly question - do you mean add the breed on import? For example:
cobbler distro add --arch=x86 --breed=fedora12 ...
Thanks,
Scot
----- Original Message -----
From: "John Eckersberg" <jeckersb(a)redhat.com>
To: cobbler(a)lists.fedorahosted.org
Sent: Tuesday, November 17, 2009 3:19:51 PM GMT -05:00 US/Canada Eastern
Subject: Re: Support for Fedora 12?
On 11/17/2009 03:15 PM, Scot Floess wrote:
> I just downloaded the i386/x86_64 Fedora 12 ISOs...
>
> I see in import:
>
> --os-version for breed redhat must be one of rhel2.1, rhel3, rhel4,
> rhel5, fedora5, fedora6, fedora7, fedora8, fedora9, fedora10, fedora11,
> generic24, generic26, other, given was fedora12
>
> I've not tried to install 12 as of yet - anything I need to do special?
> Or will there be an update to Cobbler to support 12?
>
> Thanks!
>
> Scot
>
>
> --
> Make It So Number One
>
>
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
I've just applied James Laska's patches to master that adds support for
Fedora 12 and 13. This will be included in the next 2.0.X release but
as a workaround you can just add fedora12 and fedora13 to the list of
breeds in the meantime.
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
--
Make It So Number One
14 years, 5 months
Support for Fedora 12?
by Scot Floess
I just downloaded the i386/x86_64 Fedora 12 ISOs...
I see in import:
--os-version for breed redhat must be one of rhel2.1, rhel3, rhel4, rhel5, fedora5, fedora6, fedora7, fedora8, fedora9, fedora10, fedora11, generic24, generic26, other, given was fedora12
I've not tried to install 12 as of yet - anything I need to do special? Or will there be an update to Cobbler to support 12?
Thanks!
Scot
--
Make It So Number One
14 years, 5 months
Cobbler + Hudson / Cruse Control
by Aaron Lippold
Hi Guys,
My team is looking at Hudson for CI, has anyone used Cobber + Hudson /
other for developer testing etc. I would guess that someone has done
this already but I didn't find any wiki entries on it.
Thanks,
Aaron
14 years, 5 months
Newbie question
by Diego M. Vadell
Hi List,
I have installed Cobbler in a Fedora11 server, and successfully installed
Fedora11 via PXE into another server. I configured Cobbler
* mounting the Fedora11 DVD
* cobbler import --name=Fedora11 --mirror=/mnt/
* cobbler sync
* cobbler system add --name=XXX --mac=XX:XX:XX:XX:XX:XX
--profile=Fedora11-x86_64
Not a problem.
Now I want to add one RPM, ipmitool, which didn't came into the Fedora11
DVD. Do I have to make a custom repository and add it to the profile? I
tried putting it into /var/www/cobbler/ks_mirror/Fedora11/Packages and
running cobbler reposync --only=Fedora11-x86_64 , but I still get the same
message: "You have specified that the package 'ipmitool' should be
installed. This package does not exists. Would you like to continue or abort
your installation?" when PXE booting.
Thanks in advance, and sorry for the (fundamental) question,
-- Diego.
14 years, 5 months
cobbler import results in wrong distro name
by Jens Ahrens
Hi everybody,
I'm using cobbler-2.0.1-1 on a RedHat 5.3 clone (Scientific Linux).
The problem comes with importing a distro from a loop-mounted dvd-image:
bash> mkdir Centos5.4-x86_64/
bash> mount -o loop CentOS-5.4-x86_64.iso Centos5.4-x86_64/
bash> cobbler import --path=Centos5.4-x86_64/ --name=Centos5.4-x86_64
--arch=x86_64
won't work - I have to use the full path - should be easy to fix this
bash> cobbler import --path=/localscratch/Isos/Centos5.4-x86_64/
--name=Centos5.4-x86_64 --arch=x86_64
---------------------------------------------------------------------------------------------------------------------
ask started: 2009-11-11_155754_import
task started (id=Media import, time=Wed Nov 11 15:57:54 2009)
running: rsync -a '/localscratch/Isos/Centos5.4-x86_64/'
/localscratch/cobbler/ks_mirror/Centos5.4-x86_64
--exclude-from=/etc/cobbler/rsync.exclude --progress
building file list ...
804 files to consider
./
repodata/
repodata/comps.xml
941644 100% 173.35MB/s 0:00:00 (xfer#1, to-check=7/804)
repodata/filelists.xml.gz
3478717 100% 122.87MB/s 0:00:00 (xfer#2, to-check=5/804)
repodata/other.xml.gz
10845962 100% 107.74MB/s 0:00:00 (xfer#3, to-check=3/804)
repodata/primary.xml.gz
1130874 100% 10.37MB/s 0:00:00 (xfer#4, to-check=1/804)
repodata/repomd.xml
1296 100% 12.17kB/s 0:00:00 (xfer#5, to-check=0/804)
sent 16426701 bytes received 142 bytes 32853686.00 bytes/sec
total size is 644355841 speedup is 39.23
returned: 0
adding distros
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64/images/xen for
distro signature
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64/images for
distro signature
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64 for distro
signature
found content (breed=redhat) at /l
skipping import, as distro name already exists: images-xen-x86_64
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64/images/pxeboot
for distro signature
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64/images for
distro signature
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64 for distro
signature
found content (breed=redhat) at /l
creating new distro: images-x86_64
creating new profile: images-x86_64
associating repos
traversing distro images-x86_64
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64/images/pxeboot
for distro signature
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64/images for
distro signature
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64 for distro
signature
found content (breed=redhat) at /l
descent into /localscratch/cobbler/ks_mirror/Centos5.4-x86_64
processing repo at : /localscratch/cobbler/ks_mirror/Centos5.4-x86_64
need to process repo/comps: /localscratch/cobbler/ks_mirror/Centos5.4-x86_64
looking for
/localscratch/cobbler/ks_mirror/Centos5.4-x86_64/repodata/*comps*.xml
running: createrepo -c cache -s sha --groupfile
/localscratch/cobbler/ks_mirror/Centos5.4-x86_64/repodata/comps.xml
/localscratch/cobbler/ks_mirror/Centos5.4-x86_64
This option is deprecated
635/635 - CentOS/audiofile-0.2.6-5.x86_64.rpm
Saving Primary metadata
Saving file lists metadata
Saving other metadata
returned: 0
associating kickstarts
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64/images/pxeboot
for distro signature
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64/images for
distro signature
scanning /localscratch/cobbler/ks_mirror/Centos5.4-x86_64 for distro
signature
found content (breed=redhat) at /l
*** TASK COMPLETE ***
------------------------------------------------------------------------------------------------------------------------------------
One thing about the output is strange and might be a hint on what's
going wrong:
skipping import, as distro name already exists: images-xen-x86_64
Although I explicitly give the name (--name=Centos5.4-x86_64) cobbler
does not name the distro accordingly:
bash> cobbler list
distros:
images-x86_64
images-xen-x86_64
profiles:
images-x86_64
images-xen-x86_64
systems:
repos:
images:
When I then rename the distros and profiles with:
bash> cobbler distro rename --name=images-x86_64
--newname=Centos5.4-x86_64
bash> cobbler distro rename --name=images-xen-x86_64
--newname=Centos5.4-xen-x86_64
bash> cobbler profile rename --name=images-x86_64
--newname=Centos5.4-x86_64
bash> cobbler profile rename --name=images-xen-x86_64
--newname=Centos5.4-xen-x86_64
bash> cobbler profile edit --name=Centos5.4-x86_64
--distro=Centos5.4-x86_64
bash> cobbler profile edit --name=Centos5.4-xen-x86_64
--distro=Centos5.4-xen-x86_64
a cobbler list shows:
distros:
Centos5.4-x86_64
Centos5.4-xen-x86_64
profiles:
Centos5.4-x86_64
Centos5.4-xen-x86_64
systems:
repos:
images:
But all the entries in $webdir/links/ are gone. Like this a replication
to a second server won't work anymore, because it relies on the entries
in that directory.
My question - is this a bug or am I doing something wrong.
Cheers,
Jens
14 years, 5 months