Description of problem: When settings up SPW 1.8 to kickstart machines over TFTP/DHCP, I had to manually copy menu.c32 and pxelinux.0 from the syslinux-tftpboot package to /var/lib/tftpboot. Version-Release number of selected component (if applicable): 1.8
We need more details. What OS and version is this, what version of syslinux-tftpboot, what errors did you get when you did not do the copy?
Here is more details, I just so happen to have to deploy it at work. The installed version of Spacewalk is 1.8. 1. Install RHEL 6.3 x86_64, minimal install without the @base group. 2. Install spacewalk-postgresql 3. Configure Spacewalk. 4. Start xinetd (enable it also with chkconfig) to provide tftp support. 5. Install syslinux-tftpboot. 6. Boot VM. I get the error provided in the screenshot (tftp-boot-error.png). In order to resolve that issue, I had to copy the files located under /tftpboot to /var/lib/tftpboot. Possible solution: 1. Document this better. 2. The installer takes care of that.
Created attachment 666750 [details] tftp boot error
(In reply to comment #2) > Here is more details, I just so happen to have to deploy it at work. The > installed version of Spacewalk is 1.8. > > 1. Install RHEL 6.3 x86_64, minimal install without the @base group. > 2. Install spacewalk-postgresql > 3. Configure Spacewalk. > 4. Start xinetd (enable it also with chkconfig) to provide tftp support. This is suspicious. The installer (spacewalk-setup) should have asked you Cobbler requires tftp and xinetd services be turned on for PXE provisioning functionality. Enable these services and enabled them for you automatically. What happened that they were not enabled?
I did select yes to that option to enable the support.
(In reply to comment #5) > I did select yes to that option to enable the support. So what did happen our your system that they were not enabled on your installation after running spacewalk-setup and you had to enable it manually?
I had this same issue, but solved it by copying menu.c32 and pxelinux.0 in place of the symlinks. Tftp's configuration specifies -s before the directory /var/lib/tftpboot; this basically chroots the tftpd server in /var/lib/tftpboot, and it can't access the symlinks in /usr/share...
I'm confirming this issue is reproducible with current Spacewalk nightly (to be 2.1).
After some consideration, I decided to close this report with WONTFIX. Yes, tftp-server is by default configured to chroot into /var/lib/tftpboot and syslinux-tftpboot puts the pxelinux.0 (and friends) into /tftpboot, but if this is to be considered a bug, it's more a problem of the default tftp-server configuration than anything else.
This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug.