Bug 790212

Summary:	Canceling export makes pulp server unresponsive to some commands
Product:	[Retired] Pulp	Reporter:	James Slagle <jslagle>
Component:	z_other	Assignee:	Todd Sanders <tsanders>
Status:	CLOSED WORKSFORME	QA Contact:	Preethi Thomas <pthomas>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	jason.dobies, mhrivnak, tsanders
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:	2013-09-27 14:17:03 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 James Slagle 2012-02-13 22:50:40 UTC

I tried exporting a repo, and immediately cancelling it:

[slagle@veeone ~]$ pulp-admin repo export --id candlepin-x86_64 -t /tmp/candlepin --overwrite && pulp-admin repo cancel_export --id candlepin-x86_64
Export on repository candlepin-x86_64 started
Use "repo export --status" to check on the progress
Export for repository candlepin-x86_64 is being canceled

After running this command, "repo export --status" and "task list" never return from the server, they just hang indefinitely.  You have to "service pulp-server restart" to make the server responsive again to these commands.

I was able to reproduce 3 times, although it didn't reproduce one of the times I tried.

Comment 1 Jay Dobies 2012-04-17 15:00:47 UTC

Moving out of 1.1 based on possibility to encounter this v. time to fix.

Comment 2 Pradeep Kilambi 2012-04-17 15:14:52 UTC

so investigated the issue and found that cancel exports are still using legacy cancel approach in tasking. legacy cancel has the tendency to lock up which is whats causing this issue.

so our approach to fix this would be to implement a custom cancel for Exporter. we'll probably have a cancel override in the base_exporter, which sets a flag. We can check this flag in various content exports and raise a cancelException. Also we would want to clean up the already exported data. This could be optional.

Comment 88 Michael Hrivnak 2013-09-27 14:17:03 UTC

This no longer seems to be a problem.