[JBoss JIRA] (JBIDE-25665) It is not possible to update from 4.5.1. to 4.5.2.Final using Check for Update
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25665?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-25665.
------------------------------
Fix Version/s: 4.5.2.Final
(was: 4.5.3.AM1)
Resolution: Rejected
Closing - rejected. This isn't a problem, it's a function of how updates work. If Check for Updates won't do proper remediation, there's always another way to do an update via a fresh installation.
> It is not possible to update from 4.5.1. to 4.5.2.Final using Check for Update
> ------------------------------------------------------------------------------
>
> Key: JBIDE-25665
> URL: https://issues.jboss.org/browse/JBIDE-25665
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.2.Final
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 4.5.2.Final
>
> Attachments: CheckForUpdates.png
>
>
> It is not possible to update to 4.5.2.Final using "Check for Update". Check for Update is not able to find any remedy for this conflict:
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss JAX-RS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.0.v20180105-1426)
> Software currently installed: JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.feature.feature.group 1.9.101.v20170822-1704)
> Only one of the following can be installed at once:
> JBoss WebServices Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.ui 2.0.0.v20180105-1426)
> JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.ui 1.9.101.v20170822-1704)
> Cannot satisfy dependency:
> From: JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.feature.feature.group 1.9.101.v20170822-1704)
> To: org.jboss.tools.ws.ui [1.9.101.v20170822-1704]
> Cannot satisfy dependency:
> From: JBoss JAX-RS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.0.v20180105-1426)
> To: org.jboss.tools.ws.ui [2.0.0.v20180105-1426]
> {code}
> !CheckForUpdates.png|thumbnail!
> It is maybe caused by separation of SOAP from jbosstools-webservices (JBIDE-24880).
> This process is routinely tested and the test passed on Friday/Monday, but unfortunately I made a mistake. I installed JBT 4.5.1 from Eclipse Marketplace, then I added staging update site and executed Check for Update which passed without any problems. But I didn't realize that JBT 4.5.1 added stable update site for 4.5.1, which was used together with 4.5.2 update site, so it was able to resolve that conflict. So I apologize for this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25665) It is not possible to update from 4.5.1. to 4.5.2.Final using Check for Update
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25665?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25665:
------------------------------------
If you can do the update via remediation then there's no problem. That's the whole reason p2 added remediation in the first place.
Another workaround: uninstall 4.5.1, then install 4.5.2.
> It is not possible to update from 4.5.1. to 4.5.2.Final using Check for Update
> ------------------------------------------------------------------------------
>
> Key: JBIDE-25665
> URL: https://issues.jboss.org/browse/JBIDE-25665
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.2.Final
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM1
>
> Attachments: CheckForUpdates.png
>
>
> It is not possible to update to 4.5.2.Final using "Check for Update". Check for Update is not able to find any remedy for this conflict:
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss JAX-RS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.0.v20180105-1426)
> Software currently installed: JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.feature.feature.group 1.9.101.v20170822-1704)
> Only one of the following can be installed at once:
> JBoss WebServices Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.ui 2.0.0.v20180105-1426)
> JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.ui 1.9.101.v20170822-1704)
> Cannot satisfy dependency:
> From: JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.feature.feature.group 1.9.101.v20170822-1704)
> To: org.jboss.tools.ws.ui [1.9.101.v20170822-1704]
> Cannot satisfy dependency:
> From: JBoss JAX-RS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.0.v20180105-1426)
> To: org.jboss.tools.ws.ui [2.0.0.v20180105-1426]
> {code}
> !CheckForUpdates.png|thumbnail!
> It is maybe caused by separation of SOAP from jbosstools-webservices (JBIDE-24880).
> This process is routinely tested and the test passed on Friday/Monday, but unfortunately I made a mistake. I installed JBT 4.5.1 from Eclipse Marketplace, then I added staging update site and executed Check for Update which passed without any problems. But I didn't realize that JBT 4.5.1 added stable update site for 4.5.1, which was used together with 4.5.2 update site, so it was able to resolve that conflict. So I apologize for this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25611 at 1/25/18 5:26 AM:
-------------------------------------------------------------------
[~jeffmaury] the port should be exposed in the (new) pod (not the deployment config) once you set the dc in "debug" mode via the 2 env vars (dev_mode and debug_port).
!image-2018-01-25-10-49-09-369.png!
I now switched to CDK 3.3 (from 3.2) and it behaves fine for me, exposes the debug port once the dc is in "debug" mode.
To sum up the current situtation:
|| product || versions || Status ||
| cdk 3.2 | minishift v1.7.0+204ce19, CDK v3.2.0-1 | {color:green}OK{color} |
| cdk 3.3 | OpenShift Master: v3.7.14 Kubernetes
Master: v1.7.6+a08f5eeb62 | {color:green}OK{color} |
| OpenShift Online | OpenShift Master: v3.7.23 (online version 3.6.0.32.1)
Kubernetes Master: v1.7.6+a08f5eeb62 | {color:red}NOT OK{color} |
| open.pass.redhat.com | OpenShift Master: v3.6.173.0.83
Kubernetes Master: v1.6.1+5115d708d7 | {color:green}OK{color} |
was (Author: adietish):
[~jeffmaury] the port should be exposed in the (new) pod (not the deployment config) once you set the dc in "debug" mode via the 2 env vars (dev_mode and debug_port).
!image-2018-01-25-10-49-09-369.png!
I now switched to CDK 3.3 (from 3.2) and it behaves fine for me, exposes the debug port once the dc is in "debug" mode.
To sum up the current situtation:
|| product || versions || Status ||
| cdk 3.2 | minishift v1.7.0+204ce19, CDK v3.2.0-1 | {color:green}OK{color} |
| cdk 3.3 | OpenShift Master: v3.7.14 Kubernetes Master: v1.7.6+a08f5eeb62 | {color:green}OK{color} |
| OpenShift Online | OpenShift Master: v3.7.23 (online version 3.6.0.32.1)
Kubernetes Master: v1.7.6+a08f5eeb62 | {color:red}NOT OK{color} |
| open.pass.redhat.com | OpenShift Master: v3.6.173.0.83
Kubernetes Master: v1.6.1+5115d708d7 | {color:green}OK{color} |
> Server adapter: timeouts when starting into "Debug" on OpenShift Online
> -----------------------------------------------------------------------
>
> Key: JBIDE-25611
> URL: https://issues.jboss.org/browse/JBIDE-25611
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.3.AM1
>
> Attachments: error-waiting-for-new-pod.png, image-2018-01-24-18-58-29-159.png, image-2018-01-25-10-49-09-369.png, pod-ports-cdk.png, pod-ports-online.png, port-missing.png
>
>
> # ASSERT: have an account on OpenShift Online
> # EXEC: create a new application via template nodejs-mongo-persistent
> # EXEC: have the project imported into the workspace and the server adapter for it created
> # ASSERT: you have a new server adapter for your app in state [stopped]
> # EXEC: start the adapter into "Debug"
> Result:
> The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog:
> !error-waiting-for-new-pod.png!
> In the Eclipse log you'll find the following:
> {code}
> org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25611 at 1/25/18 5:25 AM:
-------------------------------------------------------------------
[~jeffmaury] the port should be exposed in the (new) pod (not the deployment config) once you set the dc in "debug" mode via the 2 env vars (dev_mode and debug_port).
!image-2018-01-25-10-49-09-369.png!
I now switched to CDK 3.3 (from 3.2) and it behaves fine for me, exposes the debug port once the dc is in "debug" mode.
To sum up the current situtation:
|| product || versions || Status ||
| cdk 3.2 | minishift v1.7.0+204ce19, CDK v3.2.0-1 | {color:green}OK{color} |
| cdk 3.3 | OpenShift Master: v3.7.14 Kubernetes Master: v1.7.6+a08f5eeb62 | {color:green}OK{color} |
| OpenShift Online | OpenShift Master: v3.7.23 (online version 3.6.0.32.1)
Kubernetes Master: v1.7.6+a08f5eeb62 | {color:red}NOT OK{color} |
| open.pass.redhat.com | OpenShift Master: v3.6.173.0.83
Kubernetes Master: v1.6.1+5115d708d7 | {color:green}OK{color} |
was (Author: adietish):
[~jeffmaury] the port should be exposed in the (new) pod (not the deployment config) once you set the dc in "debug" mode via the 2 env vars (dev_mode and debug_port).
!image-2018-01-25-10-49-09-369.png!
I now switched to CDK 3.3 (from 3.2) and it behaves fine for me, exposes the debug port once the dc is in "debug" mode.
To sum up the current situtation:
|| product || versions || Status ||
cdk 3.2 | minishift v1.7.0+204ce19, CDK v3.2.0-1| {color:green}OK{color} |
cdk 3.3 | OpenShift Master: v3.7.14 Kubernetes Master: v1.7.6+a08f5eeb62 | {color:green}OK{color} |
OpenShift Online | OpenShift Master: v3.7.23 (online version 3.6.0.32.1)
Kubernetes Master: v1.7.6+a08f5eeb62 | {color:red}NOT OK{color} |
open.pass.redhat.com | OpenShift Master: v3.6.173.0.83
Kubernetes Master: v1.6.1+5115d708d7 | {color:green}OK{color} |
> Server adapter: timeouts when starting into "Debug" on OpenShift Online
> -----------------------------------------------------------------------
>
> Key: JBIDE-25611
> URL: https://issues.jboss.org/browse/JBIDE-25611
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.3.AM1
>
> Attachments: error-waiting-for-new-pod.png, image-2018-01-24-18-58-29-159.png, image-2018-01-25-10-49-09-369.png, pod-ports-cdk.png, pod-ports-online.png, port-missing.png
>
>
> # ASSERT: have an account on OpenShift Online
> # EXEC: create a new application via template nodejs-mongo-persistent
> # EXEC: have the project imported into the workspace and the server adapter for it created
> # ASSERT: you have a new server adapter for your app in state [stopped]
> # EXEC: start the adapter into "Debug"
> Result:
> The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog:
> !error-waiting-for-new-pod.png!
> In the Eclipse log you'll find the following:
> {code}
> org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25611 at 1/25/18 5:23 AM:
-------------------------------------------------------------------
[~jeffmaury] the port should be exposed in the (new) pod (not the deployment config) once you set the dc in "debug" mode via the 2 env vars (dev_mode and debug_port).
!image-2018-01-25-10-49-09-369.png!
I now switched to CDK 3.3 (from 3.2) and it behaves fine for me, exposes the debug port once the dc is in "debug" mode.
To sum up the current situtation:
|| product || versions || Status ||
cdk 3.2 | minishift v1.7.0+204ce19, CDK v3.2.0-1| {color:green}OK{color} |
cdk 3.3 | OpenShift Master: v3.7.14 Kubernetes Master: v1.7.6+a08f5eeb62 | {color:green}OK{color} |
OpenShift Online | OpenShift Master: v3.7.23 (online version 3.6.0.32.1)
Kubernetes Master: v1.7.6+a08f5eeb62 | {color:red}NOT OK{color} |
open.pass.redhat.com | OpenShift Master: v3.6.173.0.83
Kubernetes Master: v1.6.1+5115d708d7 | {color:green}OK{color} |
was (Author: adietish):
[~jeffmaury] the port should be exposed in the (new) pod (not the deployment config) once you set the dc in "debug" mode via the 2 env vars (dev_mode and debug_port).
!image-2018-01-25-10-49-09-369.png!
I now switched to CDK 3.3 (from 3.2) and it behaves fine for me, exposes the debug port once the dc is in "debug" mode.
To sum up the current situtation, cdk 3.2 & 3.3 work fine for me but OpenShift Online does not.
> Server adapter: timeouts when starting into "Debug" on OpenShift Online
> -----------------------------------------------------------------------
>
> Key: JBIDE-25611
> URL: https://issues.jboss.org/browse/JBIDE-25611
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.3.AM1
>
> Attachments: error-waiting-for-new-pod.png, image-2018-01-24-18-58-29-159.png, image-2018-01-25-10-49-09-369.png, pod-ports-cdk.png, pod-ports-online.png, port-missing.png
>
>
> # ASSERT: have an account on OpenShift Online
> # EXEC: create a new application via template nodejs-mongo-persistent
> # EXEC: have the project imported into the workspace and the server adapter for it created
> # ASSERT: you have a new server adapter for your app in state [stopped]
> # EXEC: start the adapter into "Debug"
> Result:
> The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog:
> !error-waiting-for-new-pod.png!
> In the Eclipse log you'll find the following:
> {code}
> org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25510) Server adapter: restarting into "Debug" fails on OpenShift Online
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25510?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25510.
---------------------------------
Closing. Restarting server adapter in debug is now working.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.3.0.AM1
Build id: AM1-v20180125-0740-B1898
Build date: 20180125-0740
> Server adapter: restarting into "Debug" fails on OpenShift Online
> -----------------------------------------------------------------
>
> Key: JBIDE-25510
> URL: https://issues.jboss.org/browse/JBIDE-25510
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.2.AM3
>
> Attachments: image-2017-12-14-11-29-56-975.png
>
>
> steps:
> # ASSERT: have an application running that you create from "wildfly:latest" builder image
> # ASSERT: source imported to your workspace and a server adapter for it
> # EXEC: (re-)start the adapter into "Debug"
> Result:
> !image-2017-12-14-11-29-56-975.png!
> In Eclipse log you find the following:
> {code}
> org.eclipse.core.runtime.CoreException: Could update resource wildfly.
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.send(OpenShiftDebugMode.java:385)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.updateDc(OpenShiftDebugMode.java:214)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:169)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:98)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: com.openshift.restclient.OpenShiftException: Exception trying to PUT https://console.starter-us-east-2.openshift.com/oapi/v1/namespaces/adieti... response code: 422 DeploymentConfig "wildfly" is invalid: spec.template.spec.containers[0].livenessProbe: Required value: must specify a handler type
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
> at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> at okhttp3.RealCall.execute(RealCall.java:57)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:257)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:221)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:209)
> at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:315)
> at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.send(OpenShiftDebugMode.java:383)
> ... 11 more
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-12-14 11:07:12.397
> !MESSAGE Could update resource wildfly.
> !STACK 0
> com.openshift.restclient.OpenShiftException: Exception trying to PUT https://console.starter-us-east-2.openshift.com/oapi/v1/namespaces/adieti... response code: 422 DeploymentConfig "wildfly" is invalid: spec.template.spec.containers[0].livenessProbe: Required value: must specify a handler type
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
> at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> at okhttp3.RealCall.execute(RealCall.java:57)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:257)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:221)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:209)
> at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:315)
> at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.send(OpenShiftDebugMode.java:383)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.updateDc(OpenShiftDebugMode.java:214)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:169)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:98)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25000:
------------------------------------------
I can reproduce this on our internal instance at *https://open.pass.openshift*.com
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.x
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25611 at 1/25/18 4:53 AM:
-------------------------------------------------------------------
[~jeffmaury] the port should be exposed in the (new) pod (not the deployment config) once you set the dc in "debug" mode via the 2 env vars (dev_mode and debug_port).
!image-2018-01-25-10-49-09-369.png!
I now switched to CDK 3.3 (from 3.2) and it behaves fine for me, exposes the debug port once the dc is in "debug" mode.
To sum up the current situtation, cdk 3.2 & 3.3 work fine for me but OpenShift Online does not.
was (Author: adietish):
[~jeffmaury] the port should be exposed in the (new) pod (not the deployment config) once you set the dc in "debug" mode via the 2 env vars (dev_mode and debug_port).
!image-2018-01-25-10-49-09-369.png!
I now switched to CDK 3.3 (from 3.2) and it behaves fine for me, exposes the debug port once the dc is in "debug" mode.
So tu sum up the current situtation, cdk 3.2 & 3.3 work fine for me but OpenShift Online does not.
> Server adapter: timeouts when starting into "Debug" on OpenShift Online
> -----------------------------------------------------------------------
>
> Key: JBIDE-25611
> URL: https://issues.jboss.org/browse/JBIDE-25611
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.3.AM1
>
> Attachments: error-waiting-for-new-pod.png, image-2018-01-24-18-58-29-159.png, image-2018-01-25-10-49-09-369.png, pod-ports-cdk.png, pod-ports-online.png, port-missing.png
>
>
> # ASSERT: have an account on OpenShift Online
> # EXEC: create a new application via template nodejs-mongo-persistent
> # EXEC: have the project imported into the workspace and the server adapter for it created
> # ASSERT: you have a new server adapter for your app in state [stopped]
> # EXEC: start the adapter into "Debug"
> Result:
> The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog:
> !error-waiting-for-new-pod.png!
> In the Eclipse log you'll find the following:
> {code}
> org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25578) Can't use WildFly 11 with JDK 9 and Dynamic Web Module 4
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25578?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25578.
---------------------------------
Closing. Creating Dynamic web project and selecting Java 9 in project facets is working.
Dynamic Web Module is not part of Java EE 7 and it is not supported by WildFly and EAP.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.3.0.AM1
Build id: AM1-v20180125-0740-B1898
Build date: 20180125-0740
> Can't use WildFly 11 with JDK 9 and Dynamic Web Module 4
> --------------------------------------------------------
>
> Key: JBIDE-25578
> URL: https://issues.jboss.org/browse/JBIDE-25578
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.2.Final
> Reporter: Lukáš Valach
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.5.2.Final
>
>
> WildFly 11 should support JDK 9 but it seems that DevStudio don't count with it. It is not possible to choose WF 11 as a runtime when Java 9 is choosen in project facets.
> Try this:
> * Install and run JBT or DevStudio against Java 9
> * create Dynamic Web Project
> ** choose WF 11 as target runtime
> ** click Finish
> * right click on created project -> Properties -> Project Facets
> * note that it is configured to use Java 1.8, not Java 9 and you are not able to select Java 9.
> * open Targeted Runtimes tab
> * deselect WF 11 and click Apply
> * open Project Facets tab
> * now it is possible to choose Java 9, so do it, select Java 9 and click Apply
> * open Targeted Runtimes tab
> * Wildfly 11 isn't available, it is hidden.
> The same problem is with Dynamic Web Module 4, it is not possible to use it with WF 11.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25611 at 1/25/18 4:52 AM:
-------------------------------------------------------------------
[~jeffmaury] the port should be exposed in the (new) pod (not the deployment config) once you set the dc in "debug" mode via the 2 env vars (dev_mode and debug_port).
!image-2018-01-25-10-49-09-369.png!
I now switched to CDK 3.3 (from 3.2) and it behaves fine for me, exposes the debug port once the dc is in "debug" mode.
So tu sum up the current situtation, cdk 3.2 & 3.3 work fine for me but OpenShift Online does not.
was (Author: adietish):
[~jeffmaury] could be an change that we missed in minishift versions. I switched back to cdk-320 when I faced the springboot permission problems. Online is running an OpenShift version that's matching the cdk in version 3.3.0. Testing it.
> Server adapter: timeouts when starting into "Debug" on OpenShift Online
> -----------------------------------------------------------------------
>
> Key: JBIDE-25611
> URL: https://issues.jboss.org/browse/JBIDE-25611
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.3.AM1
>
> Attachments: error-waiting-for-new-pod.png, image-2018-01-24-18-58-29-159.png, image-2018-01-25-10-49-09-369.png, pod-ports-cdk.png, pod-ports-online.png, port-missing.png
>
>
> # ASSERT: have an account on OpenShift Online
> # EXEC: create a new application via template nodejs-mongo-persistent
> # EXEC: have the project imported into the workspace and the server adapter for it created
> # ASSERT: you have a new server adapter for your app in state [stopped]
> # EXEC: start the adapter into "Debug"
> Result:
> The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog:
> !error-waiting-for-new-pod.png!
> In the Eclipse log you'll find the following:
> {code}
> org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months