Created attachment 448511 [details] ks-post.log Description of problem: Satellite 5.3 fails to kickstart register a guest when the kickstart is cloned and the base channel is switched. When the client has been kickstarted, ks-post.log includes this error (reproduced environment): [start] Error Message: Conflicting base channels Error Class Code: 63 Error Class Info: Conflicting activation tokens Explanation: An error has occurred while processing your request. If this problem persists please enter a bug report at bugzilla.redhat.com. If you choose to submit the bug report, please be sure to include details of what you were trying to do when this error occurred and details on how to reproduce this problem. [/end] Version-Release number of selected component (if applicable): Satellite 5.3 How reproducible: 1. Clone kickstart 2. Select different base channel 3. Assign activation key with base channel different from kickstart from which new kickstart was cloned. 4. Kickstart system Expected results: Kickstart without registration errors. Additional info: Already exists a BZ# https://bugzilla.redhat.com/show_bug.cgi?id=538435 for Spacewalk that looks the same issue. If possible, the customer is asking to backport the solution to Satellite 5.3.
This happens as well in 5.4
Please be so kind and add a few key words to the Technical Notes of this Bugzilla entry using the following structure: Cause: Consequence: Fix: Result: For details, see: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks
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: Consequence: Fix: Result:
Filling up Technical Notes.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1,11 @@ Cause: - +Cloning a channel wouldn't properly clone the activation key and wouldnt update the default session key properly Consequence: - +If cloning a kickstart and selecting a +different base channel in the newly cloned kickstart, with an activation +key that uses a different base channel, kickstarting a system using this +newly cloned profile fails. Fix: - +Clone the session key properly, when kickstart gets cloned. -Result:+Result: +Successful kickstart under listed circumstances.
Verified: RHEL5, RHEL4 - s390x, x86_64
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-0189.html