[RTFACT-14083] During repository removal, remove repository entries from the database before removing the repo from the config descriptor Created: 13/Apr/17 Updated: 10/Feb/19 Resolved: 25/Apr/18
|Project:||Artifactory Binary Repository|
|Component/s:||Artifact Storage, Configuration|
|Reporter:||Uriah Levy||Assignee:||Lior Gur (Inactive)|
|Sprint:||Leap 30, Leap 32, Leap 33, Leap 34|
Currently our repository removal process can be broken into two steps:
1.Remove the repository and the references of the repo from the config descriptor
This process is sometimes problematic. Occasionally, customers will attempt to delete a repo and the deletion will error out, leaving the repo references in the database (as if it wasn't removed), but the repo will not show in the repositories list (or on the config descriptor) since step #1 did actually complete.
If the step order was different, than the user could re-attempt to delete the repo following an error.
|Comment by Alex Dvorkin [ 18/Jul/18 ]|
Reopening the task.
Locked row for deletion
As a result, after delete in UI, the error popped, row remained in DB (artdb.nodes) but not in web UI grid