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.
DescriptionBrad Buckingham
2012-02-01 21:10:12 UTC
Description of problem:
Observing issues creating/managing System Templates in Katello when the same
name is used for repositories across multiple products.
The implementation for the UI is using repo name; however, it needs to be updated to use ID (which is unique).
Version-Release number of selected component (if applicable):
git master
How reproducible:
always
Steps to Reproduce:
1. create provider
2. create product 1 (e.g. custom1), repo A (e.g. repo1)
3. create product 2 (e.g. custom2), repo A (e.g. repo1)
4. create a system template, add 1 instance of repo1 to it (from either product) and save it
5. download/export the TDL
Actual results:
the exported TDL contains both repos... for example:
<repositories>
<repository name="repo1">
<url>
https://localhost/pulp/repos/ACME_Corporation/Library/custom/custom1/repo1
</url>
<persisted>No</persisted>
</repository>
<repository name="repo1">
<url>
https://localhost/pulp/repos/ACME_Corporation/Library/custom/custom2/repo1
</url>
<persisted>No</persisted>
</repository>
</repositories>
Expected results:
Since the user selected only 1 repo, there should only be 1 associated with and this should be reflected in the exported TDL as well.
Additional info:
commit - 9d098492575049fcf5688fd9faf5ee48eb9d8383
For system templates, a user may add a specific repo to a template by:
1. from the content tree on the left, select (+Add) for the desired repo
2. from the template tree on the right, navigate to 'Repositories', enter characters in to the auto-complete search box... once presented with a list of repositories that match (which also indicates which products they are part of), select the desired repo from the list and click +Add
Note: for option 2, if the user types the repo name and clicks add (without selecting from the dropdown), Katello will add all repos that match that name to the template. This is necessary as Katello cannot decipher which one the user actually wanted to select.