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:
Deleting a resource and creation a new one might lead to conflicts when the deletion is not finished yet
Version-Release number of selected component (if applicable):
6.0.3
How reproducible:
sometimes
Steps to Reproduce:
1. delete a repository
2. right after doing so, create a new repository with the same name
Actual results:
Duplicate resource: Default_Organization-snap2-tools
Expected results:
Resource is not allowed to be created till the old resource is still being orchestrated
Comment 1RHEL Program Management
2014-08-13 12:03:12 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Moving to POST since upstream bug http://projects.theforeman.org/issues/7333 has been closed
-------------
David Davis
Applied in changeset commit:katello|8d28f67b1cfc1cef06e5da77194cdba3a25c4a8e.
I would suggest marking this BZ as verified, as the main goal of this (which was fixed) was not getting into creation process when there is already deletion going on (which indeed happened).
I would suggest openening a new BZ asking for better error message when there is a name conflict, but deletion in progress
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, 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-2015:1592