Bug 536872

Summary:	No way to stop content sync
Product:	[Other] RHQ Project	Reporter:	Corey Welton <cwelton>
Component:	Content	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED WORKSFORME	QA Contact:	Corey Welton <cwelton>
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	jmatthew, whayutin
Target Milestone:	---	Keywords:	SubBug
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	sprint_1
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-30 17:23:52 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:	565635

Description Corey Welton 2009-11-11 16:42:02 UTC

Description of problem:
If user wants to stop content sync -- for example, if s/he deletes a syncing content provider -- the sync appears to continue.  There is no way to stop a content sync.

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


How reproducible:
Every time.


Steps to Reproduce:
1.  Add content provider
2.  Begin syncing a large channel
3.  Delete content provider
4.  View server logs.
  
Actual results:
Content continues to sync

Expected results:
* Content stop syncing
* Perhaps we need an overall "stop sync" functional button/whatever, too.


Additional info:

Comment 1 wes hayutin 2010-02-16 16:55:59 UTC

Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug

Comment 2 wes hayutin 2010-02-16 17:01:03 UTC

making sure we're not missing any bugs in rhq_triage

Comment 3 John Matthews 2010-02-18 15:34:46 UTC

Around Sprint #3/#4 the core team added the ability to Cancel a Content Sync.

Moving this to MODIFIED so it can be tested/closed by QA.

Comment 4 Corey Welton 2010-03-29 17:32:25 UTC

Mass-move to ON_QA

Comment 5 Corey Welton 2010-03-30 17:23:52 UTC

QA Closing - Essentially untestable.