Description of problem: The kickstart setting "Re-connect to the existing system profile. Do not create a new system profile." does not work. Kickstarting an already-registered system results in a new system profile on the Satellite. Version-Release number of selected component (if applicable): spacewalk-java-1.2.39-29.el5sat How reproducible: 100% Steps to Reproduce: 1. Create a kickstart profile with the following setting: System Details > Details > "Re-connect to the existing system profile. Do not create a new system profile." 2. Kickstart a new system, using this kickstart profile. 3. Kickstart the system again, using the same kickstart profile. Actual results: A new system profile is created during the second kickstart. Expected results: The first system profile should be re-used during the second kickstart. Additional info: A bash scripting error in the snippet keep_system_id appears to be the problem. The following one-line change to /var/lib/rhn/kickstarts/snippets/keep_system_id resolved the issue in my testing: # diff -pruN keep_system_id.orig keep_system_id --- keep_system_id.orig 2010-10-12 15:37:45.000000000 -0400 +++ keep_system_id 2010-12-20 17:39:49.000000000 -0500 @@ -7,7 +7,7 @@ rhn_keys_found=no insmod /lib/jbd.o insmod /lib/ext3.o -if [ -f /lib/ext4.o ]; +if [ -f /lib/ext4.o ]; then insmod /lib/ext4.o fi
This was fixed in spacewalk.git: bb3183abcf9d69bba1092d8104c456b2e3e996f7
The kickstart setting "Delete the existing system profile and create a new system profile." does not work either, it also depends on the snippet keep_system_id.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause kickstart snippet typo Consequence Kickstart snippet keep_system_id didn't work Result keep_system_id shall work in kickstart profiles like expected
*** Bug 684102 has been marked as a duplicate of this bug. ***
Thanks Cliff
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0362.html