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:
When you delete some repository IN SYNC in !custom provider! and then create another with the same name, it fails with Pulp error 409.
Version-Release number of selected component (if applicable):
katello-all-0.1.318-1.el6cf.noarch
pulp-1.0.4-1.el6.noarch
Steps to Reproduce:
1. Start syncing some repository of your choice
2. Now go to the Custom content providers (it still syncs meanwhile), click on that repository and remove it.
3. Try to create a new repository with the same name.
4. Error appears.
Actual results:
Flash message appears -> Pulp::Repository: 409 Conflict "A repository with the id, redhat-RHEL6-RHEL6_3, already exists" (PUT /pulp/api/repositories/)
Expected results:
New repository with the same name.
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM. If this is a mistake feel free to re-open.