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: