[jbosstools-issues] [JBoss JIRA] (JBIDE-23358) OpenShift Explorer: Pod status is not reflecting reality

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-23358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13308294#comment-13308294 ] 

Andre Dietisheim commented on JBIDE-23358:
------------------------------------------

[~mlabuda] sure, many things can go wrong, but then we need a reliable way to reproduce this. So my guess is that this would be the case where you use a local docker image (one that's not available in dockerhub) and not push it. Correct?

> OpenShift Explorer: Pod status is not reflecting reality
> --------------------------------------------------------
>
>                 Key: JBIDE-23358
>                 URL: https://issues.jboss.org/browse/JBIDE-23358
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.2.AM2
>            Reporter: Marián Labuda
>              Labels: openshift_v3
>             Fix For: 4.4.x
>
>         Attachments: pod_status.png
>
>
> When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods". Refresh of a project or service does not help.
> !pod_status.png!



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)