Bug 669778

Summary: Kickstart cloning bug - conflicting base channels.
Product: [Community] Spacewalk Reporter: Andy Speagle <andy.speagle>
Component: ServerAssignee: Michael Mráka <mmraka>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 1.2CC: tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-28 15:25:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 653453    

Description Andy Speagle 2011-01-14 18:32:43 UTC
Description of problem:
What I'm experiencing is that if I clone a kickstart and select 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, gives the following error during registration:

Error Message:
    Conflicting base channels
Error Class Code: 63
Error Class Info: Conflicting activation tokens

Version-Release number of selected component (if applicable):
This is happening in v1.2 of Spacewalk but was equally broken in past versions.

How reproducible:
Every time.

Steps to Reproduce:
What I believe the problem is... is that the "auto-generated" (cobbler?)
activation key that is created when I clone the kickstart, is set to use
the base channel of the kickstart from which it was cloned and is not
being updated when I select a different base channel.  So, between that
cloned auto-gen activation key and my selected organizational activation
key, the base channels are in conflict.

I can show this by creating a brand new kickstart from scratch, with the
base channel selected initially as the new base channel.  I setup the
kickstart that is identical in every way to the cloned kickstart, from
what can be shown in the WebUI.  This "from-scratch" kickstart works
perfectly.  So, I assert that the problem must be with the cloned
auto-gen activation key that's not visible in the WebUI, but only via:

cobbler profile <profile>
  
Actual results:
Error Message:
    Conflicting base channels
Error Class Code: 63
Error Class Info: Conflicting activation tokens

Expected results:
Successful registration.

Additional info:

Comment 1 Tomas Lestach 2011-01-28 15:25:29 UTC

*** This bug has been marked as a duplicate of bug 538435 ***