Hello,
We recently started using cobbler and Spacewalk together, and have run into an
interesting issue. The way Spacewalk and cobbler work together create
interesting path names under /tftpboot for the images that it needs to boot
from during installation.
Example:
/tftpboot/images/centos-55-x86_64:1:SpacewalkDefaultOrganization is one of our
default install locations. Now, we had been able to do some small scale
installs, but yesterday decided to go big (let's say some where over several
hundred nodes). These nodes have dual interfaces, so we carefully put them
into cobbler (cobbler system add --name.....). Once we were done, nothing can
install now. It seems that tftp has an issue all of the sudden with the
colons in the path, deciding that the colons are service/host names, not path
names. This whole thing had been working until we started to add those
several hundred or more nodes.
I have run cobbler sync several times, restarted cobblerd, and no errors seem
to be reported anywhere.
Here is the output from cobbler sync where it is doing the copying/hardlinks
for the tftpboot/images directrories:
copying bootloaders
copying distros
copying files for distro: centos-55-x86_64:1:SpacewalkDefaultOrganization
copying: /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/vmlinuz -> /tftpboot/images/centos-55-x86_64:1:
SpacewalkDefaultOrganization/vmlinuz
copying: /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/initrd.img -> /tftpboot/images/centos-55-x86_64
:1:SpacewalkDefaultOrganization/initrd.img
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/vmlinuz -> /var/www/cobbler/images/centos-55-
x86_64:1:SpacewalkDefaultOrganization/vmlinuz
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/initrd.img -> /var/www/cobbler/images/centos-55-
x86_64:1:SpacewalkDefaultOrganization/initrd.img
copying files for distro: centos-55-x86_64xen:1:SpacewalkDefaultOrganization
copying: /var/satellite/distro-trees/CentOS-5.5-x86_64/os/images/xen/vmlinuz -
/tftpboot/images/centos-55-x86_64xen:1:SpacewalkDefaultOrganization/vmlinuz
copying:
/var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/initrd.img -> /tftpboot/images/centos-55-
x86_64xen:1:SpacewalkDefaultOrganization/initrd.img
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/vmlinuz -> /var/www/cobbler/images/centos-55-
x86_64xen:1:SpacewalkDefaultOrganization/vmlinuz
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/initrd.img -> /var/www/cobbler/images/centos-55-
x86_64xen:1:SpacewalkDefaultOrganization/initrd.img
copying files for distro: Centos-5_5-x86_64:1:SpacewalkPublicCert
copying: /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/vmlinuz -> /tftpboot/images/Centos-5_5-
x86_64:1:SpacewalkPublicCert/vmlinuz
copying: /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/initrd.img -> /tftpboot/images/Centos-5_5-
x86_64:1:SpacewalkPublicCert/initrd.img
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/vmlinuz -> /var/www/cobbler/images/Centos-5_5-
x86_64:1:SpacewalkPublicCert/vmlinuz
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/pxeboot/initrd.img -> /var/www/cobbler/images/Centos-5_5-
x86_64:1:SpacewalkPublicCert/initrd.img
copying files for distro: Centos-5_5-x86_64xen:1:SpacewalkPublicCert
copying: /var/satellite/distro-trees/CentOS-5.5-x86_64/os/images/xen/vmlinuz -
/tftpboot/images/Centos-5_5-x86_64xen:1:SpacewalkPublicCert/vmlinuz
copying: /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/initrd.img -> /tftpboot/images/Centos-5_5-
x86_64xen:1:SpacewalkPublicCert/initrd.img
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/vmlinuz -> /var/www/cobbler/images/Centos-5_5-
x86_64xen:1:SpacewalkPublicCert/vmlinuz
trying hardlink /var/satellite/distro-trees/CentOS-5.5-
x86_64/os/images/xen/initrd.img -> /var/www/cobbler/images/Centos-5_5-
x86_64xen:1:SpacewalkPublicCert/initrd.img
copying images
generating PXE configuration files
Has anyone seen anything like this, or is there some limitation or change that
is needed to be made in a config script some where? Any direction would be
appreciated.
Norman Weathers