Bug 1160244 - can not delete oscap scan
Summary: can not delete oscap scan
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Stephen Herr
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat570-triage
TreeView+ depends on / blocked
 
Reported: 2014-11-04 12:28 UTC by Jan Hutař
Modified: 2014-11-13 15:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-10 10:52:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Hutař 2014-11-04 12:28:43 UTC
Description of problem:
I can not delete oscap scan.


Version-Release number of selected component (if applicable):
Satellite-5.7.0-RHEL6-re20141031.0-x86_64


How reproducible:
always


Steps to Reproduce:
1. Create system with OpenSCAP scan
2. System -> <your_system> -> Audit
3. Check checkbox for that scan, click "Remove Selected Scans" and then "Confirm"


Actual results:
0 SCAP Scan(s) deleted. 1 SCAP Scan(s) retained


Expected results:
That scap scan should be deleted


Additional info:
If I'm doing something wrong, please let me know.

This is a problem in Satellite 5.6.0 as well, so not a regression.

Comment 1 Tomas Lestach 2014-11-10 10:52:12 UTC
Closing as duplicate of Bug 1059775.

*** This bug has been marked as a duplicate of bug 1059775 ***

Comment 2 Grant Gainey 2014-11-13 15:58:02 UTC
Actually, no, this is NOT a dup - it's 'working as designed'.

The behavior above ("1 SCAP Scan(s) retained") means that the scan being deleted, is either newer than the required-retention-period, or the organization that owns the scan has been configured to not allow deletion at all.

See https://<fqdn>/rhn/admin/multiorg/OrgConfigDetails.do?oid=<OID>

for setting these options. The defaults are 'allow deletes' and '90 day retention'.

I'm going to re-close as "NOTABUG"


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