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.
Created attachment 557533[details]
katello log with full traceback
Description of problem:
Seems that we cannot have a product with the same name in different Orgs.
Version-Release number of selected component (if applicable):
Katello Version: 0.1.195-1.el6
How reproducible:
Steps to Reproduce:
1. Create Org1 with a product Prod1
2. Create Org2 with a product Prod1 (same as the one above
3.
Actual results:
Seeing this error message:
Runtime Error Could not execute JDBC batch update at org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError:2,598
Expected results:
Additional info:
Removing Prod1 from Org1 and then adding it to Org2 works. See attached log.
This error is caused by candlepin not allowing to have two products with the same name. I'm investigating if they could remove the uniqueness constraint.
We're waiting for candlepin bug 788940. Once it is fixed it will be possible to create products with the same name (in different orgs) also in Katello.
Name uniqueness constraint was removed from products in candlepin-0.5.23
With this version it is possible to have same name for products in different orgs.
Created attachment 557533 [details] katello log with full traceback Description of problem: Seems that we cannot have a product with the same name in different Orgs. Version-Release number of selected component (if applicable): Katello Version: 0.1.195-1.el6 How reproducible: Steps to Reproduce: 1. Create Org1 with a product Prod1 2. Create Org2 with a product Prod1 (same as the one above 3. Actual results: Seeing this error message: Runtime Error Could not execute JDBC batch update at org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError:2,598 Expected results: Additional info: Removing Prod1 from Org1 and then adding it to Org2 works. See attached log.