[
https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi...
]
Marián Labuda updated JBIDE-22603:
----------------------------------
Steps to Reproduce:
ASSERT: Have running CDK (I am using CDK 2.1 with virtualbox box on Fedora 22, Vagrant
version 1.7.2) *This is mandatory, because it is not happening when using remote OS3
server*
EXEC: Create a new connection to CDK OpenShift (openshift-dev username).
EXEC: Create a project under the connection (it's enough to have just project, no
resources are necessary).
RESULT: There is plenty of OpenShift WatchManager jobs periodically created, running and
getting finished.
EXPECTED RESULT: There are OpenShift WatchManager jobs spawned and finished.
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
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)