Bug 1308963 - Newly added parameters (PARTITION_EVENT_PURGE and RESOURCE_CONFIG_HISTORY_PURGE) do not have a description and it seems they do not work
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core Server (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
Blocks: 1308960
  Show dependency treegraph
Reported: 2016-02-16 10:08 EST by bkramer
Modified: 2016-02-16 10:08 EST (History)
1 user (show)

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 bkramer 2016-02-16 10:08:59 EST
Description of problem:
In System Settings page in RHQ 4.12 (equivalent of JBoss ON 3.3.5) there are two new parameters: PARTITION_EVENT_PURGE and RESOURCE_CONFIG_HISTORY_PURGE. These parameters are mandatory but by default their value is not set. Also, although, we can assume what the meaning of these parameters are, there are no description on the page. 

When setting both parameters to 1 - I assumed that all partition events older then a day would be deleted. However, this is not a case. 

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

How reproducible:

Steps to Reproduce:
1. Install RHQ
2. Navigate to RHQ UI -> Administration -> System Settings and set PARTITION_EVENT_PURGE and RESOURCE_CONFIG_HISTORY_PURGE to 1;
3. Save newly added values (having in mind a workaround from the Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1290436);
4. Wait for the Data Purge Job;

Actual results:
Nothing has been deleted. To confirm this, navigate to RHQ UI -> Administration -> Partition Events and confirm that the Total Rows number is not changed;

Expected results:
All events older then a day are deleted.

Additional info:

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