Bug 1035677

Summary: pxe boot on symlink
Product: [Community] Spacewalk Reporter: PerfectWeb <office>
Component: ServerAssignee: Michael Mráka <mmraka>
Status: CLOSED EOL QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.1CC: e.minguez, office
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-21 11:50:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description PerfectWeb 2013-11-28 09:50:36 UTC 
Description of problem:
The pxe boot doesnt work because the tftpboot folder contains symlink to the actual pxelinux.0 from syslinux package. If the symlink is replaced with a copy of the source pxelinux.0, it works

Version-Release number of selected component (if applicable):


How reproducible:
remove all from tftpboot and then run cobbler sync

Actual results:
pxe boot fails cause the pxelinux.0 is a symlink and is not downloaded

Expected results:
to boot

Additional info:
Comment 1 Jan Pazdziora 2013-12-02 08:21:15 UTC 
What OS and OS version are these?

Does the cobbler sync pass?

Is that possibly an SELinux issue? Is there anything interesting in /var/log/audit/audit.log?
Comment 2 PerfectWeb 2013-12-02 08:46:22 UTC 
CentOS 6.4 x86_64 
Everything works except that when there is symlinked the pxe writes that the file not found on pxe boot
Comment 3 minWi 2014-01-25 23:25:33 UTC 
As a workaround, you can create a simple cobbler trigger script like:

cat /var/lib/cobbler/triggers/sync/post/fixbz1035677.sh 

#!/bin/sh
rm -f /var/lib/tftpboot/pxelinux.0
rm -f /var/lib/tftpboot/menu.c32
cp /usr/share/syslinux/menu.c32 /var/lib/tftpboot/menu.c32
cp /usr/share/syslinux/pxelinux.0 /var/lib/tftpboot/pxelinux.0


Noticed I've added menu.c32 because it fails to me too.
Comment 5 Michael Mráka 2019-10-21 11:50:53 UTC 
Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.