Bug 1287979 - Question mark is shown beside status in pod table
Summary: Question mark is shown beside status in pod table
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Management Console
Version: 3.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-03 08:27 UTC by Yanping Zhang
Modified: 2016-05-12 17:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-12 17:09:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yanping Zhang 2015-12-03 08:27:59 UTC
Description of problem:
On web console, check pod status under "Browse"->"Pods", there is a question mark beside the pod status for each pod in table.

Version-Release number of selected component (if applicable):
$ openshift version
openshift v1.1-311-gb6ea411
kubernetes v1.1.0-origin-1107-g4c8e6f4
etcd 2.1.2

How reproducible:
Always

Steps to Reproduce:
1.Create app in project.
$ oc create -f /data/src/github.com/openshift/origin/examples/sample-app/application-template-stibuild.json -n prozyp
template "ruby-helloworld-sample" created
$ oc new-app ruby-helloworld-sample -n prozyp

2.Check pod status under "Browse"->"Pods" on web console
3.

Actual results:
2.There is a question mark beside the pod status for each pod in table.


Expected results:
2.Should show suitable mark for different status, but not a curious question mark for every pod.

Additional info:

Comment 1 Samuel Padgett 2015-12-03 19:01:36 UTC
https://github.com/openshift/origin/pull/6182

Comment 2 Yanping Zhang 2015-12-04 08:35:48 UTC
Will have a check after pull 6182 merged.

Comment 3 Yanping Zhang 2015-12-07 04:21:25 UTC
Have checked on devenv-rhel7_2888.
# openshift version
openshift v1.1-354-g43aa4a4
kubernetes v1.1.0-origin-1107-g4c8e6f4
etcd 2.1.2
Now all the icons in pod table are shown correctly, so move the bug to Verified.


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