Created attachment 366583 [details] Example ks.cfg that produces this error. For security reasons some parts were replaced by "..." (mostly single sign-on configuration) but the ks.cfg should work like this. wizard-created, btw. Description of problem: As my workmate Marcus reported[1] on the spacewalk-list (we see this on both, our Spacewalk and our Satellite server): "even after an successful Kickstart process, the SystemID file is not deleted from /tftpboot/pxelinux.cfg/, causing an installation-rerun on every boot of the affected machine." We've also opened a ticket at RH Support regarding this issue (will link to this bug from there). [1] https://www.redhat.com/archives/spacewalk-list/2009-October/msg00189.html Version-Release number of selected component (if applicable): - Satellite 5.3.0 - Spacewalk 0.6 Both are in evaluation and therefore updated at least once a day (i.e. fully up to date) How reproducible: Always Steps to Reproduce: 1. In the WebUI, look at a system and go to the Provisioning Scheduling. Make your choices and start the re-provisioning. 2. Wait until the kickstart process has finished (and reboot). 3. See that the kickstart process will restart. 4. On the Satellite/Spacewalk, do: ls /tftpboot/pxelinux.cfg/ and see the SystemIDs are still there. Actual results: infinite re-provisioning Expected results: one-time re-provisioning Additional info:
We've been wondering how the process actually is intended to work i.e. what in the ks process is notifying the satellite to rm the file and so on. We have a very restrictive policy running on the satellite and might be blocking something.
So I think the step you are missing is to enable pxe_just_once in /etc/cobbler/settings and then restart cobbler. With this enabled, a simple wget is appended to the end of the kickstart which will trigger on the server to set that system to localboot within the pxe configuration. This should solve your issue. I'll go ahead and close this bug, but feel free to reopen it if this does not correct your issue. Thanks, -Justin
Hey Justin :) Thanks for the hint - that should be far better documented (in the satellite, not in cobbler or within cobbler's settings file th). I actually wonder - wouldn't it be sane to make this the default? I mean how likely is it that someone wants to re-provision a system over and over again? Thanks, Sandro / red_alert
1) pxe_just_once by default 2) document its usage in Satellite Ref/Guide Bonus, not needed.... 3) Expose in UI?? Cliff.
I think this should be fixed as part of eeac1d23705f7176d3213412525bdae38403af30 Will test with the next nightly. -Justin
# VERIFIED confirm: the sat540 current iso (Satellite-5.4.0-RHEL5-re20101001.1) contains pxe_just_once: 1 in /etc/cobbler/settings while the default value for sat530 servers was set to "0".
The 5.4.0 RHN Satellite and RHN Proxy release has occurred. This issue has been resolved with this release. RHEA-2010:0801 - RHN Satellite Server 5.4.0 Upgrade https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10332 RHEA-2010:0803 - RHN Tools enhancement update https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10333 RHEA-2010:0802 - RHN Proxy Server 5.4.0 bug fix update https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10334 RHEA-2010:0800 - RHN Satellite Server 5.4.0 https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10335 Docs are available: http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/index.html Regards, Clifford