Red Hat Bugzilla – Bug 1461505
Issues with readinessChecks
Last modified: 2017-06-15 22:05:01 EDT
Description of problem: When the pod is scheduled on this node, the kubelet can't reach the spring-boot within 1s. It is *not* that the app takes to long to answer, because we don't see any healt check requests coming in in the logs. So the time must get lost on the way between pod and kubelet. Version-Release number of selected component (if applicable): oc version oc v3.4.1.18 kubernetes v1.4.0+776c994 features: Basic-Auth GSSAPI Kerberos SPNEGO openshift v3.4.1.18 kubernetes v1.4.0+776c994 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
can you provide your pod yaml output and the node logs for when this event occurs?
Possible dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1457399 ?
@Jimmi - this does look similar, but I am unable to verify without more information. @Gabor - which logs are you referring to? your application's logs are showing no checks made, or the node logs are showing no probe attempts? for now, i am going to mark as a duplicate of 1457399 as my reading of this is that the application is never getting the request. if we get more information later, we can triage further. *** This bug has been marked as a duplicate of bug 1457399 ***