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

Bug 2000586

Summary:	`[sig-node] Probing container should be ready immediately after startupProbe succeeds` is permafailing on OKD 4.9
Product:	OpenShift Container Platform	Reporter:	Vadim Rutkovsky <vrutkovs>
Component:	Node	Assignee:	Ryan Phillips <rphillips>
Node sub component:	Kubelet	QA Contact:	Sunil Choudhary <schoudha>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	aos-bugs
Version:	4.9
Target Milestone:	---
Target Release:	4.9.0
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:	2021-09-02 20:41:08 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 Vadim Rutkovsky 2021-09-02 12:45:51 UTC

See https://prow.ci.openshift.org/job-history/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-okd-4.9-e2e-aws

Example job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-okd-4.9-e2e-aws/1433108936696795136

[sig-node] Probing container should be ready immediately after startupProbe succeeds [Suite:openshift/conformance/parallel] [Suite:k8s]

fail [github.com/onsi/ginkgo.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Sep  1 17:34:43.764: Pod became ready in 10.230333973s, more than 5s after startupProbe succeeded. It means that the delay readiness probes were not initiated immediately after startup finished.

Comment 1 Vadim Rutkovsky 2021-09-02 20:41:08 UTC

OKD 4.9 nightlies used kubelet from 4.8, marking as dupe of the related bug

*** This bug has been marked as a duplicate of bug 2000584 ***