Bug 1559168 - Curator should not use a default run time of midnight
Summary: Curator should not use a default run time of midnight
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.9.0
Assignee: ewolinet
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-21 21:23 UTC by ewolinet
Modified: 2018-06-18 18:29 UTC (History)
7 users (show)

Fixed In Version: openshift-ansible:v3.9.14
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-06-18 18:07:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-ansible pull 7616 0 None None None 2018-03-22 14:20:38 UTC

Description ewolinet 2018-03-21 21:23:46 UTC 
Description of problem:
With the default time of curation for curator being midnight, it causes elasticsearch to work hard with also creating new indices for the day.

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

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Curator runs by default at midnight

Expected results:
Curator should run later than midnight

Additional info:
Comment 1 ewolinet 2018-03-21 21:32:19 UTC 
https://github.com/openshift/openshift-ansible/pull/7602
Comment 2 Jeff Cantrill 2018-03-22 02:13:10 UTC 
*** Bug 1559162 has been marked as a duplicate of this bug. ***
Comment 3 Anping Li 2018-03-22 03:05:10 UTC 
@ewolinet， Is that a mutually exclusive case for https://bugzilla.redhat.com/show_bug.cgi?id=1559219?
Comment 4 Jeff Cantrill 2018-03-22 14:20:38 UTC 
3.9 https://github.com/openshift/openshift-ansible/pull/7616
Comment 6 Anping Li 2018-03-23 05:35:28 UTC 
The fix works with openshift-ansible:v3.9.14.

# oc get dc logging-curator -o yaml |grep -A 1 CURATOR_RUN
        - name: CURATOR_RUN_HOUR
          value: "3"
        - name: CURATOR_RUN_MINUTE
          value: "30"
        - name: CURATOR_RUN_TIMEZONE
          value: UTC
Note You need to log in before you can comment on or make changes to this bug.