Bug 1460041 - Creating a scheduled job with schedule: "*/0 * * * *" causes various components to hang [NEEDINFO]
Creating a scheduled job with schedule: "*/0 * * * *" causes various componen...
Status: CLOSED CURRENTRELEASE
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
3.4.1
Unspecified Unspecified
medium Severity high
: ---
: ---
Assigned To: Maciej Szulik
DeShuai Ma
: Unconfirmed
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-08 18:03 EDT by Eric Jones
Modified: 2017-06-27 19:22 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-06-27 19:22:27 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
maszulik: needinfo? (erjones)


Attachments (Terms of Use)

  None (edit)
Description Eric Jones 2017-06-08 18:03:36 EDT
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.