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.
Description of problem:
Importing a custom repository with different label but same name causes validation error
Version-Release number of selected component (if applicable): Satellite 6.11
How reproducible:
Always
Steps to Reproduce:
In Upstream Satellite/Org
1. `hammer organization create --name=upstream` (any org name will do)
2. `hammer product create --name=custom --organization=upstream`
3. `hammer repository create --name=repo --content-type=yum --url=https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/ --product=custom --organization=upstream`
4. `hammer repository synchronize --name=repo --product=custom --organization=upstream`
5. Export via `hammer content-export complete repository --name=repo --product=custom --organization=upstream`
Make a note of the path
In the Downstream Satellite/org
1. `hammer organization create --name=downstream` (any org name will do)
2. Create a product with same name but different label -> `hammer product create --name=custom --organization=downstream --label=custom_product`
3. `hammer content-import repository --path=<import path> --organization=downstream`
Expected:
Successful import with a new custom product and repo added to it
Actual:
Could not import the archive.:
Validation failed: Name has already been taken for a product in this organization.
Additional Info:
The same error occurs if a custom repository is created with same name but different label
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.12 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:8506