Bug 670970

Summary: Unable to create an activation key in child org with the same name in base org
Product: Red Hat Satellite 5 Reporter: David Glaser <dsglaser>
Component: UsabilityAssignee: Justin Sherrill <jsherril>
Status: CLOSED DEFERRED QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 540CC: cperry
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-29 20:10:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 462714    

Description David Glaser 2011-01-19 19:36:36 UTC 
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.