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

Bug 1844376

Summary:	[k8s.io] [sig-node] Pods Extended [k8s.io] Pod Container Status should never report success for a pending container
Product:	OpenShift Container Platform	Reporter:	Petr Horáček <phoracek>
Component:	Node	Assignee:	Ryan Phillips <rphillips>
Status:	CLOSED DUPLICATE	QA Contact:	Sunil Choudhary <schoudha>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.0	CC:	aos-bugs, jdelft, jokerman, rphillips, slaznick, vlaad, wking
Target Milestone:	---	Keywords:	DeliveryBlocker, Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	[k8s.io] [sig-node] Pods Extended [k8s.io] Pod Container Status should never report success for a pending container
Last Closed:	2020-06-18 14:12:59 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 Petr Horáček 2020-06-05 09:13:03 UTC

test:
[k8s.io] [sig-node] Pods Extended [k8s.io] Pod Container Status should never report success for a pending container 

is failing frequently in CI, see search results:
https://search.svc.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bk8s%5C.io%5C%5D+%5C%5Bsig-node%5C%5D+Pods+Extended+%5C%5Bk8s%5C.io%5C%5D+Pod+Container+Status+should+never+report+success+for+a+pending+container

The test is failing 100 % of the time on multiple lanes. The issue seems to be always the same.

One of the failed jobs: https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.2/1387

Comment 1 Ryan Phillips 2020-06-05 18:21:59 UTC

Pod container statuses have been fixed in later versions (namely 4.4 and above) in Openshift. Since 4.2 is almost EOL, only critical bug fixes (CVE, etc) are being backported, so I will mark this BZ as WONTFIX.

Comment 2 Standa Laznicka 2020-06-17 11:14:36 UTC

But it's not EOL yet, so at least add a skip to the the test causing the failures in the release job since you cared enough to break it two weeks ago in https://github.com/openshift/origin/pull/25038, even if it's just to skip it, otherwise build watchers will be coming at you week after week.

Comment 5 W. Trevor King 2020-06-18 14:12:59 UTC

Closing as a dup of #1825372, which is, as far as I can tell, a dup.  Please re-open if I'm getting that wrong.

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

Comment 6 Red Hat Bugzilla 2023-09-14 06:01:47 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days