Bug 1889405 - Cronjob skips
Summary: Cronjob skips
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-controller-manager
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 3.11.z
Assignee: Maciej Szulik
QA Contact: zhou ying
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-19 15:33 UTC by Danila Kiselev
Modified: 2020-11-17 00:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Danila Kiselev 2020-10-19 15:33:56 UTC
Description of problem:

Customer experiences random skips of cronjob (supposed to work everyday). They use it to execute their own app (and they're very sure the problem is in cronjob). 

They have some problems with sosreport. 
$ sosreport --allow-system-changes -k docker.all=on -k docker.logs=on

only give some info, a lot of commands were skipped with "required kernel modules or services not present (kmods=[] services=[docker])." even with "--allow-system-changes" key. 

They tried to recreate the cronjob, still got problems.

Version-Release number of selected component (if applicable):
Openshift 3.11.200 on Atomic Host 7.7.5

How reproducible:
Rarely

Steps to Reproduce:
The issue seems to be random.

Actual results:
Cronjob doesn't work

Expected results:
Cronjob finished successfully

Comment 3 Maciej Szulik 2020-10-23 10:25:15 UTC
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.

Comment 4 Maciej Szulik 2020-11-13 10:52:50 UTC
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.


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