Description of problem: Having a valid KS profile it fails on registering the system to the Spacewalk. The system installation, fetching certificate, changes in up2date config file - all went ok, but the rhnreg_ks command failed with: --- Error Message: Could not find token 're-1-3d02d35f4e5ac69a68546e792b52b362' Error Class Code: 60 Error Class Info: The activation token specified could not be found on the server. Please retry with a valid key. --- This key seems to be the one from post-ks snippet "redhat_register" "rhnreg_ks --serverUrl=$endpoint --sslCACert=$mycert --activationkey=\$key,$redhat_management_key" (the $redhat_management_key) Version-Release number of selected component (if applicable): spacewalk-backend-1.1.42-1.el5 spacewalk-schema-1.1.19-1.el5 How reproducible: always Steps to Reproduce: 1. Get a channel synced to SW with all the necessary provisioning packages with it(koan, rhnlib, etc....) 2. Download and save in SW filesystem the necessary structure for booting (like the ones: images/pxeboot/{initrd.img,vmlinuz} etc) 3. Create a KS distribution for that channel. Point the path to that directory containing the files above. 4. Make a KS profile (switch of "VT" repository). Choose the default option "Re-connect to the existing system profile. Do not create a new system profile." in the System Details -> Details page of the ks profile created. 5. Switch on "Log custom post scripts" in the Kickstart details -> Details 6. Entitle your system with Provisioning entitlement and do the provisioning by that profile. 7. You'll never get in UI-side of the SW the finish state of the process but actually the system would be reprovisioned but NOT registered to SW. 8. Look at logged "/root/ks-post.log" there should be the messages described above. Actual results: system is provisioned but not registered to SW Expected results: system gets registered to SW Additional info: Refer personally for providing access to the systems/logs.
# COMMENT Assigning to Partha after discussing the issue with Justin.
Fixed: 3b72ce18cb12ecf446a86cc82a7e0f3926adbb76 The cause was that we were obtaining a re-activation key regardless of whether or not a reactivation key was already being used within the kickstart(Which would invalidate the one already present). The little bit of code that i added will go through all activation keys of the kickstart and if one is a reactivation key, will not try to obtain a new one.
Hey Justin, Many thanks for the fix - the package spacewalk-java-1.1.41-1.el5 fixed my issue actually. Looking forward for the proper status of the BZ for putting the issues to verified.
Spacewalk 1.1 has been released.
# VERIFIED Actually with the latest iso provided the problems were gone. (Satellite-5.4.0-RHEL5-re20100818.0-x86_64)
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