Bug 2183565

Summary:	[RFE] Support for to setup notification for long running /stopped/failed/ task
Product:	Red Hat Satellite	Reporter:	rkhadkik
Component:	Sync Plans	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.10.0	CC:	aruzicka, dsinglet, sajha
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	x86_64
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-20 10:06:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description rkhadkik 2023-03-31 16:49:39 UTC

1. Proposed title of this feature request  
>>> Sync Status notification status

2. Who is the customer behind the request?
Account: name and acct # >>> Teva / Boris Bresh and 469996
TAM customer: no
CSM customer: no
Strategic: no

3. What is the nature and description of the request? 
>> Client wants to setup notification for long running /stopped/failed/ task?

4. Why does the customer need this? (List the business requirements here) 
>>> He wants to create some cron to monitor this

5. How would the customer like to achieve this? (List the functional requirements here) 
>> NA 

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 
>> NA

7. Is there already an existing RFE upstream or in Red Hat Bugzilla? 
>> NA

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
 >> NA

9. Is the sales team involved in this request and do they have any additional input? 
>> NA

10. List any affected packages or components. 
>> NA

11. Would the customer be able to assist in testing this functionality if implemented? 
>> NA

Comment 2 rkhadkik 2023-04-03 08:41:34 UTC

The client replied with an update.

I don't want to setup crons ... this is why I asked for such functionality. 
Now only way to manage paused/pending tasks is to go to GUI and check manually. 

During upgrades I found multiple such tasks and just cancel them. 

I have question: 
What I should do when there is long-running/stopped/failed/ task?

Is it possible to setup mechanism which cancels non relevant tasks? 
For example after successful repository sync all syncs which were failed before it should be canceled as non relevant any more.

Comment 6 Adam Ruzicka 2023-05-29 10:42:16 UTC

> What I should do when there is long-running/stopped/failed/ task?

Could you please elaborate on the "long-running/stopped/failed/"?

> Is it possible to setup mechanism which cancels non relevant tasks? 

How would you define "non relevant"?

> For example after successful repository sync all syncs which were failed before it should be canceled as non relevant any more.

It feels like we're overloading terms here a little bit. "Cancel" in this context means something like "dismiss"?

Comment 7 Dana Singleterry 2023-09-20 10:06:53 UTC

Closing as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1950836

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

Comment 8 Red Hat Bugzilla 2024-01-19 04:25:18 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days