Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1461505

Summary:	Issues with readinessChecks
Product:	OpenShift Container Platform	Reporter:	Gabor Burges <gburges>
Component:	Node	Assignee:	Derek Carr <decarr>
Status:	CLOSED DUPLICATE	QA Contact:	DeShuai Ma <dma>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.4.1	CC:	aos-bugs, gburges, jdyson, jokerman, mmccomas, mwhittin
Target Milestone:	---	Keywords:	OpsBlocker
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-16 02:05:01 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 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