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.

Description of problem:
the regular OPENscap (email) reports refer to Foreman instead of Satellite

Version-Release number of selected component (if applicable):
6.2.0 snap6.2

How reproducible:
always

Steps to Reproduce:
1. set up your email config
2. go to user emai lpreferences and turn on OPENScap reports
3. receive the report

Actual results:
title: "Foreman OpenScap summary"
text: "Summary report from Foreman server at"

Expected results:
Satellite instead of Foreman in the text

Additional info:

*** Bug 1328507 has been marked as a duplicate of this bug. ***

Created attachment 1162752 [details]
openscap summart email report

VERIFIED
on sat6.2.0 beta GA13.1

- there are no more references to Foreman

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, 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/RHBA-2016:1501