[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22603:
----------------------------------
Description:
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.
was:
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.
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.
> 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
> 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)
9 years, 9 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22603:
-------------------------------------
Summary: 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
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.
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)
9 years, 9 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22603:
----------------------------------
Labels: explorer openshift_v3 (was: )
> 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
> Labels: explorer, openshift_v3
>
> 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.
> 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)
9 years, 9 months
[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-21290:
-------------------------------------------
So there is now {{vagrant service-manager box version --script-readable}} which can be called to determine the version of CDK/ADB. The VM has to be running for this to work, but I think this is the only way to properly report a version. Adding the marker file has several issues:
# The cdk.zip which maybe could be used to add it, might go away in the near future. At least that is the plan. It would be really up to the platform installers to create the marker files and add the version.
# The user could install a CDK and then upgrade it later (just the VM, not the whole install). The reported version would still be the one in the marker file.
IMO, the best solution is to get the version from the VM. Could the UI not display "unkown" until the VM is started and then update the version based on service-manager call?
> CDK 2 is detected as version 1.0
> --------------------------------
>
> Key: JBIDE-21290
> URL: https://issues.jboss.org/browse/JBIDE-21290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, runtime-detection, upstream
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.x
>
> Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png
>
>
> When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0.
> !cdk-runtime-detection.png!
> Could we change it to version 2?
> I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-20002) Explorer: Delete multiple OpenShift resources at once
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20002?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-20002:
---------------------------------------
[~jeffmaury] ah I see... I've just checked it and in JBIDE-21420 was not implemented only deletion of more projects at once but also of resources (that was not mentioned in that JIRA). So this one can be considered as done as well.
> Explorer: Delete multiple OpenShift resources at once
> -----------------------------------------------------
>
> Key: JBIDE-20002
> URL: https://issues.jboss.org/browse/JBIDE-20002
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
>
> It would be nice to have a feature allowing removing more resources at once:
> 1) Multiselect on some specific type of resource (e.g. pods) and deleting them via context menu "Delete resources..." which pop up dialog "Do you really want to delete selected resources?" with Yes, No, Cancel.
> 2) Deleting specific resources - from context menu on Pods / Builds etc. I would like to choose "Delete resources..." to remove all underlying resources.
> 3) Delete all resources. Should be accessible from context menu of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-20002) Explorer: Delete multiple OpenShift resources at once
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20002?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-20002:
------------------------------------
It is not relevant since JBIDE-21420
> Explorer: Delete multiple OpenShift resources at once
> -----------------------------------------------------
>
> Key: JBIDE-20002
> URL: https://issues.jboss.org/browse/JBIDE-20002
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
>
> It would be nice to have a feature allowing removing more resources at once:
> 1) Multiselect on some specific type of resource (e.g. pods) and deleting them via context menu "Delete resources..." which pop up dialog "Do you really want to delete selected resources?" with Yes, No, Cancel.
> 2) Deleting specific resources - from context menu on Pods / Builds etc. I would like to choose "Delete resources..." to remove all underlying resources.
> 3) Delete all resources. Should be accessible from context menu of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months