Red Hat Bugzilla – Bug 1460280
High CPU Utilization Openshift process (Origin v1.4)
Last modified: 2017-08-16 15:51 EDT
+++ This bug was initially created as a clone of Bug #1460271 +++ +++ This bug was initially created as a clone of Bug #1460260 +++ Description of problem: Description at https://github.com/openshift/origin/issues/14428 Version-Release number of selected component (if applicable): oc v1.4.0+208f053 kubernetes v1.4.0+776c994 features: Basic-Auth GSSAPI Kerberos SPNEGO How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info: Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
I have tested this on below version: openshift v3.6.121 kubernetes v1.6.1+5115d708d7 Tried to run bunch of emptyDir test cases on one scheduable node and did not find high CPU utilization. Thanks
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1716