Bug 771697

Summary: misleading error message trying to delete a repo while another repo is being deleted
Product: [Retired] Pulp Reporter: Preethi Thomas <pthomas>
Component: user-experienceAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED DUPLICATE QA Contact: Preethi Thomas <pthomas>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: skarmark
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-04 17:10:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Preethi Thomas 2012-01-04 16:46:02 UTC 
Description of problem:
if you try to delete a second repo while another is being deleted the error message says 
error:  error: operation failed: The repository, , cannot be deleted

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.delete a large repo
2. issue another delete repo soon after the first (while the first one is deleted)
3.
  
Actual results:
root@preethi ~]# pulp-admin repo delete --id=centos1
Repository [ centos1 ] being deleted

[root@preethi ~]# pulp-admin repo delete --id=centos
error:  error: operation failed: The repository, centos, cannot be deleted

From pulp.log

2012-01-04 11:51:08,156 27150:140293965870848: pulp.server.async:ERROR: async:60 Task [4c858657-36f4-11e1-9cfc-002564a85a58] Task 4c858657-36f4-11e1-9cfc-002564a85a58: RepoApi.delete(, id=centos) scheduled to run immediately conflicts with [202f7dc0-36f4-11e1-ba6c-002564a85a58] Task 202f7dc0-36f4-11e1-ba6c-002564a85a58: RepoApi.delete(, id=centos1) scheduled to run immediately and cannot be enqueued

Expected results:


Additional info:
Comment 1 Sayli Karmarkar 2012-01-04 17:10:23 UTC 

*** This bug has been marked as a duplicate of bug 769381 ***