[jbosstools-issues] [JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

[Marián Labuda (JIRA)]

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

Marián Labuda commented on JBIDE-22603:
---------------------------------------

[~adietish] I would like to address this issue ASAP. It's not annoying only from usability and user-friendliness, but this is serious issue for automated tests, I can say blocking one.

> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
>                 Key: JBIDE-22603
>                 URL: https://issues.jboss.org/browse/JBIDE-22603
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.0.Final
>            Reporter: Marián Labuda
>            Priority: Critical
>              Labels: explorer, openshift_v3
>             Fix For: 4.4.x
>
>         Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.



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