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
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.
Connecting redmine issue http://projects.theforeman.org/issues/7333 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/7333 has been closed ------------- David Davis Applied in changeset commit:katello|8d28f67b1cfc1cef06e5da77194cdba3a25c4a8e.
This is already in the downstream repo.
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
Per comment 12, I am moving this back to ON_QA. I have opened a new bug to improve the error message https://bugzilla.redhat.com/show_bug.cgi?id=1217544
This bug is slated to be released with Satellite 6.1.
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