Bug 1326276 - deletig oscap reports notif says 'Successfully deleted 0 compliance reports'
Summary: deletig oscap reports notif says 'Successfully deleted 0 compliance reports'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Marek Hulan
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1368225 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-12 10:13 UTC by Kedar Bidarkar
Modified: 2019-09-26 15:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16223 0 Normal Closed deletig oscap reports notif says 'Successfully deleted 0 compliance reports' 2020-03-31 10:11:45 UTC

Description Kedar Bidarkar 2016-04-12 10:13:45 UTC 
Description of problem:
deletig oscap reports notif says 'Successfully deleted 0 compliance reports'

Version-Release number of selected component (if applicable):
sat62-snap7.1

How reproducible:


Steps to Reproduce:
1. after 'foreman_scap_client <policy_id>' command is run on the host
2. Reports are seen under compliance reports page
3. Delete the compliance reports to note, the notif

Actual results:
deletig oscap reports notif says 'Successfully deleted 0 compliance reports'

Deleting 1 or multiple reports shows "0" compliance reports.

Expected results:

deletig oscap reports notif should specify the count appropriately , rather than the below message for any number of deleted reports.
'Successfully deleted 0 compliance reports'
Additional info:
Comment 2 Shlomi Zadok 2016-08-22 08:18:19 UTC 
Created redmine issue http://projects.theforeman.org/issues/16223 from this bug
Comment 3 Bryan Kearney 2016-09-05 14:15:21 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16223 has been resolved.
Comment 4 Ranjan Kumar 2016-09-09 14:20:35 UTC 
*** Bug 1368225 has been marked as a duplicate of this bug. ***
Comment 8 Satellite Program 2018-02-21 16:54:17 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.