Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1512473 - The Init:Error pod should not be "Pod Initializing" sandglass on pod page
The Init:Error pod should not be "Pod Initializing" sandglass on pod page
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console (Show other bugs)
3.7.0
Unspecified Unspecified
medium Severity low
: ---
: 3.9.0
Assigned To: Robb Hamilton
Yadan Pei
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-13 05:20 EST by Xingxing Xia
Modified: 2018-03-28 10:12 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The web console's pod status filter had not been updated to account for init container status after init containers were added to the platform. Consequence: As a result, the web console's pod status filter did not display init status, including and init status of error. Fix: The pod status filter has been updated to display init status. Result: If a pod has an Init:Error status, the pod status filter now outputs "Init Error" instead of "Pod Initializing".
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-28 10:12:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Pod Initializing (28.43 KB, image/png)
2017-11-13 05:20 EST, Xingxing Xia
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 None None None 2018-03-28 10:12 EDT

  None (edit)
Description Xingxing Xia 2017-11-13 05:20:14 EST
Created attachment 1351497 [details]
Pod Initializing

Description of problem:
The Init:Error pod should not be "Pod Initializing" sandglass on pod page

Version-Release number of selected component (if applicable):
v3.7.7

How reproducible:
Always

Steps to Reproduce:
1. Make a pod whose status will be Init:Error
E.g. ordering Perl image on home page with invalid git repo, the build pod will be Init:Error
$ oc get build
NAME      TYPE      FROM         STATUS                       STARTED         DURATION
perl-1    Source    Git@master   Failed (FetchSourceFailed)   5 minutes ago   3s
$ oc get pod
NAME            READY     STATUS       RESTARTS   AGE
perl-1-build    0/1       Init:Error   0          2m

2. Check _pod_ "perl-1-build" status/icon on pods list page and pod page

Actual results:
2. It shows "Pod Initializing" sandglass, making a wrong feeling the pod is still initializing

Expected results:
2. Should show error status/icon

Additional info:
Comment 3 Robb Hamilton 2018-01-26 14:26:22 EST
PR to resolve: https://github.com/openshift/origin-web-console/pull/2676
Comment 5 Xingxing Xia 2018-02-05 01:52:39 EST
Checked in OCP v3.9.0-0.36.0, now the Init:Error pod is displayed correctly "X Init Error" in pods list page and pod page
Comment 8 errata-xmlrpc 2018-03-28 10:12:08 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0489

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