Bug 1324517 - Branding - OpenSCAP email reports refer to Foreman instead of Satellite
Summary: Branding - OpenSCAP email reports refer to Foreman instead of Satellite
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Branding
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: Shimon Shtein
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-06 14:07 UTC by Roman Plevka
Modified: 2019-09-26 16:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:19:12 UTC
Target Upstream Version:

Attachments (Terms of Use)
openscap summart email report (19.14 KB, image/png)
2016-05-30 09:47 UTC, Roman Plevka 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1592879 0 unspecified CLOSED Sendmail functionality not working on satellite 2021-02-22 00:41:40 UTC

Internal Links: 1592879

Description Roman Plevka 2016-04-06 14:07:06 UTC 
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:
Comment 2 Shlomi Zadok 2016-05-29 08:24:44 UTC 
*** Bug 1328507 has been marked as a duplicate of this bug. ***
Comment 3 Roman Plevka 2016-05-30 09:47:27 UTC 
Created attachment 1162752 [details]
openscap summart email report

VERIFIED
on sat6.2.0 beta GA13.1

- there are no more references to Foreman
Comment 4 Bryan Kearney 2016-07-27 11:19:12 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, 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
Note You need to log in before you can comment on or make changes to this bug.