Description of problem:
I tried to set a specific PXEBOOTDIR using /etc/sysconfig/system-config-netboot config file.
Still /tftpboot/linux-install/ is hardcoded to /tftpboot/linux-install/ in package install scripts and in Python script /usr/share/system-config-netboot/netboot_util.py.
So when trying to run pxeos using an other PXEBOOTDIR value we still get PXE install kit created under /tftpboot/linux-install/.
nota: I ran command: pxeos -a -p FTP -D0 -s 10.13.16.1 -L /pub/rhel-5.2/tree -K ftp://10.13.16.1/pub/rhel-5.2/kickstart/ks.cfg RHEL-5.2_X86-64-test
Version-Release number of selected component (if applicable):
How reproducible: always
Steps to Reproduce:
1. install install system-config-netboot-cmd.noarch
2. change PXEBOOTDIR value in /etc/sysconfig/system-config-netboot config file
3. run pxeos and everything is still created under /tftpboot/linux-install/ instead of chosen PXEBOOTDIR value.
everything is still created by pxeos under /tftpboot/linux-install/
everything created by pxeos under chosen PXEBOOTDIR value set into /etc/sysconfig/system-config-netboot config file.
Investigating the package files I found /usr/share/system-config-netboot/netboot_util.py where PXEBOOTDIR and PXECFGDIR seems to be incorrectly defined and set.
I fixed it as follow:
[root@my_redhat_server ~]# diff /usr/share/system-config-netboot/netboot_util.py my_patched_netboot_util.py
> global PXEBOOTDIR
Still I get this error message:
# pxeos -a -p FTP -D0 -s 10.23.66.1 -L /pub/rhel-5.2/tree -K ftp://10.23.66.1/pub/rhel-5.2/kickstart/ks.cfg RHEL-5.2_X86-64-test
Traceback (most recent call last):
File "/usr/sbin/pxeos", line 603, in ?
File "/usr/sbin/pxeos", line 106, in saveOSList
bootFD=open("%s/msgs/boot.msg" % PXEBOOTDIR,"w")
IOError: [Errno 2] No such file or directory: '/var/services/tftp-root/linux-install-test//msgs/boot.msg'
Therefore I manually moved needed PXE stuff directories to my tagerted PXEDIR:
# mv /tftpboot/linux-install/* /var/services/tftp-root/linux-install/
And finaly pxeos runs smoothly setting up the PXE stuff where I want.
Therefore it looks to me like to issues to get fixed but I am not a developper.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).