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

[Marián Labuda (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marián Labuda updated JBIDE-22361:
----------------------------------
    Description: 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.  (was: 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. Service is collapsed, sometimes even several times. Upon expanding an existing service it still contains old pod (either application on build pod). So once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Application pod is visible only upon refresh of a project.)


> 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
>            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)