Bug 747975

Summary: Deleting a (possibly large) repo can intermittently fail, leaving phantom repos that can't be removed.
Product: Red Hat Satellite Reporter: Corey Welton <cwelton>
Component: APIAssignee: Bryan Kearney <bkearney>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.1CC: jconnor, mmccune
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-22 18:02:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 747354    

Description Corey Welton 2011-10-21 15:08:18 UTC 
Description of problem:
Trying to delete a large repo, I got a timeout error notification on the pulp process. Subsequent attempts to delete repo return a success message, but viewing the Product tree shows the repo as still there.

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


How reproducible:


Steps to Reproduce:
1.  Create a new provider and product
2.  Create a new repo for the product called "Fedora - Everything", using the URL "http://download.fedoraproject.org/pub/fedora/linux/releases/15/Everything/x86_64/os/" 
3.  Sync this repo.
4.  After the repo is fully synced, attempt to delete it.  Possibly, you should get a fail message.
5.  Attempt to delete repo again; observe "green" notification that it has been removed.
6. From the providers view, navigate back down to the Product tree and expand.  
Actual results:

* First, I got the error message:
"Pulp::Repository: Request Timeout (DELETE /pulp/api/repositories/ACME_Corporation-f15-x86_64_-_base/)"
* subsequently, any attempts to delete show success but the repos are still there.


Expected results:

Clean deletion

Additional info:
I'm not sure there's much we can do about the pulp timeout, but we shouldn't be able to be stuck in a half-baked state.
Comment 1 Mike McCune 2011-11-02 15:06:00 UTC 
The Pulp team is going to make delete async so our APIs need to be able to handle deletions in this new way.
Comment 2 Jason Connor 2011-12-12 21:27:57 UTC 
Repo sync is now asynchronous and returns a task status object with the 202 accepted code. 

The cli behaviour doesn't track the repo sync like, but instead retains the current behaviour of reporting the repo deleted.

Fix pushed in 87f2206e704a54f2c2efbc09cfbb4759ee5d1d8a
Comment 3 Mike McCune 2012-01-26 19:08:43 UTC 
mass ON_QA move
Comment 5 Corey Welton 2012-02-15 20:22:12 UTC 
I've not had this problem lately, and it's even harder to repro when I'm not seeing the deletion fail in the first place.  marking as verified, can reopen later if necessary.
Comment 7 Mike McCune 2013-08-16 18:12:42 UTC 
getting rid of 6.0.0 version since that doesn't exist