Bug 1754118 - "CronJob /logging-curator is taking more than 1h to complete." reported in Prometheus
Summary: "CronJob /logging-curator is taking more than 1h to complete." reported in Pr...
Keywords:
Status: CLOSED DUPLICATE of bug 1751542
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.11.z
Assignee: Pawel Krupa
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-20 20:54 UTC by Greg Rodriguez II
Modified: 2023-03-24 15:29 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-07 11:24:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Greg Rodriguez II 2019-09-20 20:54:17 UTC 
Description of problem:
"CronJob /logging-curator is taking more than 1h to complete." is being reported daily in Prometheus, however the Curator is working as expected and the Curator pod moves from "Running" status to "Completed" in under a few minutes.  Indices older than the specified number of days are deleted without issue.

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

How reproducible:
Multiple customers reporting this issue under same OCP version

Steps to Reproduce:
1. Set Curator cronjob to run once a day and allow it to run
2. Check AlertManager and find run length warning
3. Check list of indices and verify that Curator ran correctly (files deleted)
4. Verify no errant issues reported in Curator pod log

Actual results:
"CronJob /logging-curator is taking more than 1h to complete." in AlertManager although Curator runs correctly

Expected results:
There should be no notifications for the Curator cronjob if it runs correctly

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