From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

Description of problem:
If you create two or more activation keys, each activation keys has
one or more config channels associated with it then the registration
of a system using both activation keys will fail due to conflict error
messages. The files being deployed are uniq to both keys and there is
no conflicting files to be deployed. 

This seems to be an issue with no ranking/ordering being done when
multiple activation keys (with config file channels) are used together. 

If I use a single activation key with all the config file channels
then it will work as expected (when using beta channel
up2date-4.2.29-1 rpm, fails with U2 released up2date and 4.2.16-1
version). 


Version-Release number of selected component (if applicable):
RHN Satellite 3.4 and RHN Hosted 3.4

How reproducible:
Always

Steps to Reproduce:
1. Create a config channel and put a single file into it
2. Create a second config channel and put a single different file into it
3. Create an activation key with provisioning entitlement, put the
first config channel within it. Check the Schedule deployment box at
bottom.
4. Create a second activation key with provisioning entitlement, put
the second config channel within it, again checking the schedule
deployment box. 
5. On a RHEL 3 U2 installed system run command :
# rhnreg_ks --force --activationkey=xxxxxxxxxxxxxx,zzzzzzzzzzzzzzzz

where the xxxx's and zzzz's are replaced with your two activation key
strings.


Actual Results:  https://172.16.59.210/XMLRPC

# rhnreg_ks --force
--activationkey=14adb25f2c8b5c48648642083c0c7b3b,871a603b39387f1b5cf92aff79927d4b
Error Message:
    Conflicting configuration channels for tokens
`config-channel-test-key-1' and `config-channel-test-key-2'
Error Class Code: 63
Error Class Info: Conflicting activation tokens

#

Expected Results:  It would perform a test, confirm no conflicts and
if there was a conflict go with a right to left or left to right order
of precedance for the listed keys and deploy the files as expected. 

Additional info: