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 1483464 - Rename "Openscap policy summary" to "Compliance policy summary"
Summary: Rename "Openscap policy summary" to "Compliance policy summary"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-21 08:07 UTC by Marek Hulan
Modified: 2019-09-26 15:38 UTC (History)
5 users (show)

Fixed In Version: foreman_openscap-0.7.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:51:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot of UI (72.02 KB, image/png)
2017-09-17 11:16 UTC, Nikhil Kathole
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20655 0 None None None 2017-08-21 08:10:16 UTC

Description Marek Hulan 2017-08-21 08:07:26 UTC
Description of problem:

In mail notifications configuration for the user, there's a string "Openscap policy summary". It should be renamed to "Compliance policy summary" to avoid "OpenSCAP" capitalization. The notification name is stored in DB so we'll need to provide a migration for existing setups.

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

6.3

How reproducible:

100%

Steps to Reproduce:
1. see user mail notification configuration


Actual results:

there's Openscap policy summary label

Expected results:

there's Compliance policy summary label

Comment 1 Marek Hulan 2017-08-21 08:10:14 UTC
Created redmine issue http://projects.theforeman.org/issues/20655 from this bug

Comment 3 Satellite Program 2017-08-21 10:02:30 UTC
Upstream bug assigned to mhulan

Comment 4 Satellite Program 2017-08-21 10:02:33 UTC
Upstream bug assigned to mhulan

Comment 5 Satellite Program 2017-08-22 08:02:28 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20655 has been resolved.

Comment 6 Nikhil Kathole 2017-09-17 11:15:14 UTC
VERIFIED

Version Tested:
Satellite-6.3 Snap 16

steps:

1. Navigated to user's mail notification configuration

Found label named as Compliance policy summary.
(see screenshot attached)

Comment 7 Nikhil Kathole 2017-09-17 11:16:25 UTC
Created attachment 1326934 [details]
screenshot of UI

Comment 8 Satellite Program 2018-02-21 16:51:07 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/RHSA-2018:0336


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