[
https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi...
]
Marián Labuda commented on JBIDE-22361:
---------------------------------------
Ok, I have tested it on latest available JBDS build v20160515-2224-B5363. The problem with
not showing pods at current state is gone. What stayed is collapsing of nodes. Having a
service expanded and waiting till there will be an application pod, the nodes are
collapsed to project level. Changes to pod amount and their states performed via different
channel than IDE are reflected correctly in IDE. Do you wanna create a new issue for that
or are you gonna change this JIRA to be accurate with current state (collapsing of
nodes)?
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)