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 1732925 - [RFE] Satellite 6 host advisory email - content control
Summary: [RFE] Satellite 6 host advisory email - content control
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.3.5
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Perry Gagne
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-24 17:53 UTC by Dhaval Joshi
Modified: 2020-11-23 09:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-05 14:35:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 Marek Hulan 2019-07-25 08:07:00 UTC
I agree this may be a nice additional option to the errata notification. In 6.5 you could achieve similar report though through report engine. There's a report "Applicable errata" that can give you same results and supports hosts filtering. It can be triggered through API from cron and the result can be send via mail. In next version we'll have mailing support for report results built-in. Does this solve the use case? If not, what is missing.

Comment 5 Marek Hulan 2019-08-05 14:35:38 UTC
After confirmation, this can be considered resolved by report template "Applicable errata" in 6.5, closing as current release


Note You need to log in before you can comment on or make changes to this bug.