[JBoss JIRA] (JBIDE-23005) [Watcher] Server Adapter: Stuck on creating/publishing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23005:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> [Watcher] Server Adapter: Stuck on creating/publishing
> ------------------------------------------------------
>
> Key: JBIDE-23005
> URL: https://issues.jboss.org/browse/JBIDE-23005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter, upstream
> Fix For: 4.4.3.AM1
>
> Attachments: stucked_server_adapter
>
>
> When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23279) Exception generated when OS 3 connection URL is invalid
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23279?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23279:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Exception generated when OS 3 connection URL is invalid
> -------------------------------------------------------
>
> Key: JBIDE-23279
> URL: https://issues.jboss.org/browse/JBIDE-23279
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Jeff MAURY
> Labels: openshift, openshift_v3
> Fix For: 4.4.3.AM1
>
>
> EXEC: launch application wizard via file menu: New > OpenShift > OpenShift application
> EXEC: select <New Connection>
> EXEC: enter invalid URL in the host field
> ASSERT: an com.openshift.restclient.OpenShiftException: Unable to initialize client exception is logged into the console
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-20723) OpenShift 3 application is created even though Cancel button was clicked
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20723?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20723:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> OpenShift 3 application is created even though Cancel button was clicked
> ------------------------------------------------------------------------
>
> Key: JBIDE-20723
> URL: https://issues.jboss.org/browse/JBIDE-20723
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Fix For: 4.4.3.AM1
>
>
> Once the Finish button in New OpenShift Application wizard is clicked a new application is created no matter what. Even if I click on a Cancel button next to the progress bar of creation process, it looks at first like the process stopped, but it still continues and in few moments a shell with created resources is shown. Can we do something about this? Otherwise cancel button just stop eclipse job and progress bar but it does not do anything more behind it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22969:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Make sure OpenShift Tools support proxies
> -----------------------------------------
>
> Key: JBIDE-22969
> URL: https://issues.jboss.org/browse/JBIDE-22969
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Alexey Kazakov
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.3.AM1
>
> Attachments: proxy_settings.png, proxy_settings_2.png
>
>
> CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too.
> If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side.
> This issue covers:
> - testing
> - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests)
> - fixing any problems we have in OpenShift tooling regarding proxy support.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23422:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.3.AM1
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months