Bug 1844376 - [k8s.io] [sig-node] Pods Extended [k8s.io] Pod Container Status should never report success for a pending container
Summary: [k8s.io] [sig-node] Pods Extended [k8s.io] Pod Container Status should never ...
Keywords:
Status: CLOSED DUPLICATE of bug 1825372
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Ryan Phillips
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-05 09:13 UTC by Petr Horáček
Modified: 2023-09-14 06:01 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
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
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


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