Bug 2000586 - `[sig-node] Probing container should be ready immediately after startupProbe succeeds` is permafailing on OKD 4.9
Summary: `[sig-node] Probing container should be ready immediately after startupProbe ...
Keywords:
Status: CLOSED DUPLICATE of bug 2000584
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.9.0
Assignee: Ryan Phillips
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-02 12:45 UTC by Vadim Rutkovsky
Modified: 2021-09-02 20:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-02 20:41:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.