Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 862809

Summary: Product name is not unique
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: Content ManagementAssignee: Mike McCune <mmccune>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.0Keywords: Regression, Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-09 19:38:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mike McCune 2012-10-03 15:23:33 UTC 
You can create duplicate products based on name within an individual provider.  This breaks CLI and API tools that require you to look up the product based on name.  The CLI and API allow you to do the following:


katello product create --name product-one --provider test_prov --label=product-one1
katello product create --name product-one --provider test_prov --label=product-one2
katello product create --name product-one --provider test_prov --label=product-one3
katello product create --name product-one --provider test_prov --label=product-one4

this means that you can't reference the product in subsequent calls:

katello repo create --name repo-one --product product-one --url http://something/test

Lets check to see if in 1.0 product names were required to be unique and if so lets re-enforce this restriction.
Comment 1 Mike McCune 2012-10-08 18:34:18 UTC 
Note, with 1.0.1 you can't do the above:


# katello product create --name product-one --provider test_prov  --org ACME_Corporation
Successfully created product [ product-one ]
# katello product create --name product-one --provider test_prov  --org ACME_Corporation
Validation failed: Products within an organization must have unique name.

definite a regression
Comment 3 Mike McCune 2012-10-09 19:38:55 UTC 
found out we have to make product name *not* unique because of BZ:

commit a87bd08016ce785999159b2f44aae39ef5059aae
Author: Adam Price <adprice>
Date:   Tue Aug 21 09:31:26 2012 -0400

    844806 - katello incorrectly prevents products with the same name in an organization
    
    removes the uniqueness validation for product names