[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22603:
-------------------------------------
Sprint: devex #117 July 2016 (was: devex #116 June 2016)
> 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
> Assignee: Jeff MAURY
> 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)
9 years, 9 months
[JBoss JIRA] (JBIDE-21818) Too large margins in wizards
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21818:
-------------------------------------
Sprint: (was: devex #116 June 2016)
> Too large margins in wizards
> ----------------------------
>
> Key: JBIDE-21818
> URL: https://issues.jboss.org/browse/JBIDE-21818
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.x
>
> Attachments: Screenshot 2016-03-04 11.19.59.png
>
>
> Some wizard have too large margins, wasting space and making them inconsistent with the other Eclipse wizards in general.
> See attached screenshot as an example
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22626:
-------------------------------------
Sprint: devex #117 July 2016 (was: devex #116 June 2016)
> Updating deployed docker image on OpenShift does not work
> ---------------------------------------------------------
>
> Key: JBIDE-22626
> URL: https://issues.jboss.org/browse/JBIDE-22626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.4.1.AM1
>
>
> In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok.
> But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done.
> Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22362:
-------------------------------------
Sprint: devex #117 July 2016 (was: devex #116 June 2016)
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.1.AM1
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21857:
------------------------------------------
we should review and test the PR in sprint #117
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.4.x
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21857:
-------------------------------------
Sprint: devex #117 July 2016 (was: devex #116 June 2016)
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.4.x
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months