Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2183565 - [RFE] Support for to setup notification for long running /stopped/failed/ task
Summary: [RFE] Support for to setup notification for long running /stopped/failed/ task
Keywords:
Status: CLOSED DUPLICATE of bug 1950836
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Sync Plans
Version: 6.10.0
Hardware: x86_64
OS: All
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-31 16:49 UTC by rkhadkik
Modified: 2024-01-19 04:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-20 10:06:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-22574 0 None None None 2024-01-19 04:26:48 UTC

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