[jbosstools-issues] [JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher does not work

Jeff Cantrill (JIRA) issues at jboss.org
Fri May 13 13:09:00 EDT 2016


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

Jeff Cantrill commented on JBIDE-22361:
---------------------------------------

Pulled master and deployed following the referenced steps.  I saw similar behavior though the final state for me is a running pod as expected.  The part I didn't quite understand but seems tangential to this bug is:

# node collapsed down to the project
# expanding the service displays both the build and running pod
# build pod eventually disappears and only the run pod is visible

It did not react as quickly as the web, but it worked for me.  @fbricon thoughts on how I should proceed?

> OpenShift Explorer: Watcher does not work
> -----------------------------------------
>
>                 Key: JBIDE-22361
>                 URL: https://issues.jboss.org/browse/JBIDE-22361
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.0.Alpha2
>            Reporter: Marián Labuda
>            Assignee: Jeff Cantrill
>            Priority: Critical
>              Labels: explorer, openshift_v3
>
> When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Once watcher should update resources automatically, service is collapsed, also project is collapsed, but after expanding those tree items, there is still old pod. Current pod is visible only upon refresh of a project.



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



More information about the jbosstools-issues mailing list