Bug 1460041 - Creating a scheduled job with schedule: "*/0 * * * *" causes various components to hang
Summary: Creating a scheduled job with schedule: "*/0 * * * *" causes various componen...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: Maciej Szulik
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-08 22:03 UTC by Eric Jones
Modified: 2020-07-16 09:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-27 23:22:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Eric Jones 2017-06-08 22:03:36 UTC 
Description of problem:
Customer found an issue with creating a scheduled job that appears to break their OpenShift cluster as a whole.

They first noted pods not being able to pull images from the docker registry. It was also reported that certain pods that use the internal network were unable to do so. We also saw certain oc commands hang and others cause the terminal to freeze entirely.

We are able to restore everything to functional status by restarting the atomic-openshift-master-{api,controllers} services

As such we attempted to increase the log levels on the atomic-openshift-master-{api,controllers} and collected the logs I will be attaching to the bug shortly.

Version-Release number of selected component (if applicable):
openshift 3.4.1.2
Note You need to log in before you can comment on or make changes to this bug.