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 1393613 - [RFE] Notification via email when repo sync fail
Summary: [RFE] Notification via email when repo sync fail
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Notifications
Version: 6.2.4
Hardware: x86_64
OS: Linux
medium
high with 1 vote
Target Milestone: 6.15.0
Assignee: Adam Ruzicka
QA Contact: Pavel Novotny
URL:
Whiteboard:
: 1316844 1387770 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 01:17 UTC by Waldirio M Pinheiro
Modified: 2024-10-01 16:03 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-23 17:10:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 17748 0 Normal New Notification via email when repo sync fail 2022-06-23 16:43:37 UTC
Red Hat Issue Tracker SAT-20188 0 None None None 2024-02-01 08:59:07 UTC
Red Hat Issue Tracker SAT-6880 0 None None None 2024-02-01 02:26:36 UTC
Red Hat Knowledge Base (Solution) 7022546 0 None None None 2023-06-30 15:13:10 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:10:38 UTC

Description Waldirio M Pinheiro 2016-11-10 01:17:02 UTC 
Description of problem:
Customer with 5 organizations and a lot of repository to sync daily, so the big problem is, they need check everyday via webUI if all orgs concluded with successful the sync since there isn't any way to Satellite inform SysAdmin about some issue during the sync.

In the Notification (Administer - Users - <Select user> - Email Preference - Notifications, is possible to see different kinds of notification but not related to repo sync. The idea is create one new entry here to Sync Repos for example.

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

How reproducible:
100%

Steps to Reproduce:
1. Create one sync plan
2. Force one error during the sync plan *remove network for example*
3. Will possible see, SysAdmin will see the error only if access the Satellite via webUI

Actual results:
Repo without sync and SysAdmin without notification.

Expected results:
SysAdmin receiving any kind of notification.

Additional info:
Another interesting feature here should be define one number of retries, for example, if sync fail, before send one email talking about the fail, Satellite will retry 5 times.
Comment 2 Stephen Benjamin 2016-12-19 18:42:46 UTC 
Created redmine issue http://projects.theforeman.org/issues/17748 from this bug
Comment 3 Stephen Benjamin 2016-12-19 19:34:26 UTC 
*** Bug 1316844 has been marked as a duplicate of this bug. ***
Comment 4 Brad Buckingham 2017-03-08 12:16:04 UTC 
*** Bug 1387770 has been marked as a duplicate of this bug. ***
Comment 5 Bryan Kearney 2018-09-04 18:59:12 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Comment 6 Bryan Kearney 2018-09-04 19:11:02 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Comment 8 Mike McCune 2022-07-08 17:15:31 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 9 Brad Buckingham 2022-09-02 20:08:50 UTC 
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.
Comment 12 Brad Buckingham 2023-01-04 22:48:23 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 16 Bryan Kearney 2023-09-19 12:00:32 UTC 
Upstream bug assigned to aruzicka
Comment 17 Bryan Kearney 2023-09-19 12:00:37 UTC 
Upstream bug assigned to aruzicka
Comment 18 Bryan Kearney 2023-10-04 16:00:52 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/17748 has been resolved.
Comment 19 Brad Buckingham 2023-10-30 11:29:29 UTC 
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.
Comment 20 Pavel Novotny 2023-11-22 19:50:06 UTC 
Verified in Sat. stream snap 38:
satellite-6.15.0-0.3.stream.el8sat.noarch
foreman-3.9.0-0.5.develop.20231115163837git2774da2.el8sat.noarch

Verification:
1. Create a user with email set and enabled.
2. Subscribe the user to these notifications:
   * Content view promote failure 
   * Content view publish failure 
   * Capsule sync failure 
   * Repository sync failure 
3. Execute the tasks in step 2 in a fashion that each of them ends with a failure.
4. Check the user's email for new notification messages.

Result:
Each failed task results in an email notification sent to the user's address.
The email is not sent if the user is disabled or has the email disabled (Email Enabled is unchecked).


Example notification email for a repository sync failure:
~~~
Subject: [satellite] Repository product_repo_1 failed to synchronize

Synchronize repository 'product_repo_1'; product 'product_1'; organization 'Organization 1' failed.

Repo ID: 1
Repo label: product_repo_1
Product ID: 1
Product label: product_1
Task ID: 49cb79af-0ef9-4682-be68-3cfebc9ee594
Task state: stopped
Task result: warning
Task details: https://<fqdn>/foreman_tasks/tasks/49cb79af-0ef9-4682-be68-3cfebc9ee594

Errors:
- Katello::Errors::Pulp3Error: 404, message='Not Found', url=URL('http://<reposerver>/repos/nonexisting_repo/')
~~~
Comment 24 errata-xmlrpc 2024-04-23 17:10:36 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:2010
Note You need to log in before you can comment on or make changes to this bug.