Bug 771697 - misleading error message trying to delete a repo while another repo is being deleted
Summary: misleading error message trying to delete a repo while another repo is being ...
Keywords:
Status: CLOSED DUPLICATE of bug 769381
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-04 16:46 UTC by Preethi Thomas
Modified: 2013-09-09 16:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-04 17:10:23 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.