Bug 1460041
| Summary: | Creating a scheduled job with schedule: "*/0 * * * *" causes various components to hang | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Eric Jones <erjones> |
| Component: | Node | Assignee: | Maciej Szulik <maszulik> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | DeShuai Ma <dma> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.4.1 | CC: | aos-bugs, eparis, erjones, jokerman, mmccomas |
| Target Milestone: | --- | Keywords: | Unconfirmed |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-06-27 23:22:27 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 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