Bug 1016675 - Disabling of SCAP result deletion policy resets retention period
Disabling of SCAP result deletion policy resets retention period
Status: NEW
Product: Red Hat Satellite 5
Classification: Red Hat
Component: API (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jan Dobes
Red Hat Satellite QA List
Depends On:
Blocks: sat560-triage
  Show dependency treegraph
Reported: 2013-10-08 09:58 EDT by Lukas Pramuk
Modified: 2016-06-07 11:22 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lukas Pramuk 2013-10-08 09:58:22 EDT
Description of problem:
Disabling of the scap result deletion policy also resets retention period to the default (90 days). The retention period is being reset either using webui or API. 

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

How reproducible:

Steps to Reproduce:
1. >>> client.org.setPolicyForScapResultDeletion(key, 1, {'retention_period': 15, 'enabled': False})
2. >>> client.org.getPolicyForScapResultDeletion(key,1)
{'retention_period': 0, 'enabled': False}

1. Admin -> Organization -> <selected organization> -> Configuration:
check Allow Deletion of SCAP Results: [v] and then you can set value of Allow Deletion After (period in days). And hit "Update Organization" button.
2. uncheck Allow Deletion of SCAP Results: [_] and hit "Update Organization" button.

3. In both situations custom value of retention_period/"Allow Deletion After (period in days)" is discarded and replaced by the default one.

Actual results:
disabling the policy also resets retention period to the default

Expected results:
when disabling the policy retention period remains the same
Comment 1 Šimon Lukašík 2013-10-08 18:06:12 EDT
It's rather feature than bug. :)

Nevertheless if we really want to fix this feature, we need a schema change.
Comment 2 Lukas Pramuk 2013-10-09 07:04:30 EDT
This bz is an enhancement to the RFE bz #993079 (tuning of already implemented RFE)

Schema change: I  see you need to add new char(1) field to rhnOrgConfiguration table.
Comment 3 Šimon Lukašík 2016-06-07 11:22:56 EDT
I am sorry guys. I haven't been able to move this forward during last 3 years and I don't envision having time for this in the three years to come.

Resetting the assignee to the default.

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