Description of problem:

When creating an activation key in a child organization with the same name as a key that already exists in the base org, an error is produced.

Base key: provisioning (key created before multi-org existed on server, so no 1- prefix)
Child key: 3-provisioning (3- already exists as part of the prefix)
Error produced.

Base key: 1-comm (key created after multi-org existed, 1- prefix automatically created)
Child key: 3-comm (3- already exists as part of the prefix)

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


How reproducible:

Always on any keys that existed with no number prefix

Steps to Reproduce:
1. Determine a key on base or with no prefix
2. Log into a child org, try to create a child key with the same name 
3. Error produced when trying to create the key
  
Actual results:

The Key should be created since it actually doesn't match the base key (it will have a 3- prefix in the above example). 

Expected results:

The key will be created as normal. 

Additional info:

The check against the base key (or all keys) should include the child's prefix, so no collision exists would be my assumption.