Bug 1559168

Summary: Curator should not use a default run time of midnight
Product: OpenShift Container Platform Reporter: ewolinet
Component: LoggingAssignee: ewolinet
Status: CLOSED CURRENTRELEASE QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.9.0CC: aos-bugs, ewolinet, jcantril, pportant, rmeggins, smunilla, wsun
Target Milestone: ---   
Target Release: 3.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openshift-ansible:v3.9.14 Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-18 18:07:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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 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