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

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>

such as...  

redhat mgmt key      :
1-b79e0b2b365afbff80ae65a104638b05,1-rhel-x86_64-server-5-4


Version-Release number of selected component (if applicable):
v0.6

How reproducible:
Every time.

Steps to Reproduce:
1.  Clone kickstart
2.  Select different base channel
3.  Assign activation key with base channel different from kickstrat from which new kickstart was cloned.
4.  Kickstart system
  
Actual results:
Error as above.

Expected results:
Kickstart without registration errors.


Additional info: