Bug 1461505 - Issues with readinessChecks
Summary: Issues with readinessChecks
Keywords:
Status: CLOSED DUPLICATE of bug 1457399
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.4.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Derek Carr
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-14 15:53 UTC by Gabor Burges
Modified: 2023-09-14 03:59 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-16 02:05:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gabor Burges 2017-06-14 15:53:58 UTC
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:

Comment 1 Derek Carr 2017-06-14 22:01:12 UTC
can you provide your pod yaml output and the node logs for when this event occurs?

Comment 2 Jimmi Dyson 2017-06-15 11:13:39 UTC
Possible dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1457399 ?

Comment 3 Derek Carr 2017-06-16 02:05:01 UTC
@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 ***

Comment 4 Red Hat Bugzilla 2023-09-14 03:59:11 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.