[JBoss JIRA] (JBIDE-25510) Server adapter: restarting into "Debug" fails on OpenShift Online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25510?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25510:
------------------------------------------
The bug seems to be that the tooling tries to create a liveness probe. The original deployment config doesnt have a liveness probe, thus there's no need for the tooling to alter an existing liveness probe to allow debugging (the tooling alters existing liveness probes for the following reason: if a liveness probe exists, it would kill the an existing debug session if the debugger halts code execution for more than the defined probe interval. The tooling thus changes the initial delay).
> 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
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.2.Final
>
> 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)
8 years, 3 months
[JBoss JIRA] (JBIDE-25510) Server adapter: restarting into "Debug" fails on OpenShift Online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25510?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25510:
-------------------------------------
Fix Version/s: 4.5.2.Final
> 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
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.2.Final
>
> 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)
8 years, 3 months
[JBoss JIRA] (JBIDE-25510) Server adapter: restarting into "Debug" fails on OpenShift Online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25510?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25510:
-------------------------------------
Labels: openshift_v3 server_adapter (was: )
> 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
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.2.Final
>
> 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)
8 years, 3 months
[JBoss JIRA] (JBIDE-25510) Server adapter: restarting into "Debug" fails on OpenShift Online
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-25510:
----------------------------------------
Summary: 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
Priority: Critical
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)
8 years, 3 months
[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25303 at 12/14/17 4:22 AM:
--------------------------------------------------------------------
[~aurelien.pupier] imho this was a misunderstanding. Facets and OpenShift server profiles are orthogonal concerns, one does not exclude the other even though there are overlappings.
was (Author: adietish):
[~aurelien.pupier] imho this was a misunderstanding. Facets and OpenShift server profiles are orthogonal concerns, one does not exclude the other.
> Server adapter: support hot-deployment on OpenShift for SpringBoot app
> ----------------------------------------------------------------------
>
> Key: JBIDE-25303
> URL: https://issues.jboss.org/browse/JBIDE-25303
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.2.AM3
>
> Attachments: fuse-on-openshift.zip, project-deployment-assembly.png, spring-boot-demo.zip
>
>
> currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file.
> The requirements are:
> - rsync unpacked jar
> - rsync without the jar name as folder
> - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated)
> use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools":
> - there is a SpringBoot app deployed on OpenShift
> - the developer want to develop evolution of the SpringBoot app
> -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance
> -- Remote java debug should be available when the OpenShift server adapter is in debug mode.
> Steps:
> # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot)
> # EXEC: Import project within fuse-on-openshift.zip into your workspace
> # EXEC: open launch configuration and change:
> ** -Dkubernetes.master= so that it first your cdk instance
> ** -Dkubernetes.namespace= to the name of the project that you create in step 1.
> # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk)
> # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running.
> # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service)
> # ASSERT: server adapter is created and is *[started]*
> # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service)
> # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end
> {code}
> simple-route - >>> 455
> simple-route - >>> 695
> simple-route - >>> 935
> {code}
> # EXEC: In Project Explorer: open class MyTransformer and change the transform method
> # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25509) Properties: one can not select multiple resources
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-25509:
----------------------------------------
Summary: Properties: one can not select multiple resources
Key: JBIDE-25509
URL: https://issues.jboss.org/browse/JBIDE-25509
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.5.2.AM2
Reporter: Andre Dietisheim
steps:
# ASSERT: have an OpenShift app running
# EXEC: in OpenShift explorer: select the project and open up the "Properties" view. In the properties view select "Pods"
# ASSERT: there are multiple pods listed
# EXEC: try to select several ones (ex. in order to delete them)
Result:
You can only select a single entry, you cannot select several ones and ex. delete them at once.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25509) Properties: one can not select multiple resources
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25509?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25509:
-------------------------------------
Fix Version/s: 4.5.x
> Properties: one can not select multiple resources
> -------------------------------------------------
>
> Key: JBIDE-25509
> URL: https://issues.jboss.org/browse/JBIDE-25509
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Andre Dietisheim
> Labels: properties
> Fix For: 4.5.x
>
>
> steps:
> # ASSERT: have an OpenShift app running
> # EXEC: in OpenShift explorer: select the project and open up the "Properties" view. In the properties view select "Pods"
> # ASSERT: there are multiple pods listed
> # EXEC: try to select several ones (ex. in order to delete them)
> Result:
> You can only select a single entry, you cannot select several ones and ex. delete them at once.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25509) Properties: one can not select multiple resources
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25509?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25509:
-------------------------------------
Labels: properties (was: )
> Properties: one can not select multiple resources
> -------------------------------------------------
>
> Key: JBIDE-25509
> URL: https://issues.jboss.org/browse/JBIDE-25509
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Andre Dietisheim
> Labels: properties
> Fix For: 4.5.x
>
>
> steps:
> # ASSERT: have an OpenShift app running
> # EXEC: in OpenShift explorer: select the project and open up the "Properties" view. In the properties view select "Pods"
> # ASSERT: there are multiple pods listed
> # EXEC: try to select several ones (ex. in order to delete them)
> Result:
> You can only select a single entry, you cannot select several ones and ex. delete them at once.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25303:
------------------------------------------
[~aurelien.pupier] imho this was a misunderstanding. Facets and OpenShift server profiles are orthogonal concerns, one does not exclude the other.
> Server adapter: support hot-deployment on OpenShift for SpringBoot app
> ----------------------------------------------------------------------
>
> Key: JBIDE-25303
> URL: https://issues.jboss.org/browse/JBIDE-25303
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.2.AM3
>
> Attachments: fuse-on-openshift.zip, project-deployment-assembly.png, spring-boot-demo.zip
>
>
> currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file.
> The requirements are:
> - rsync unpacked jar
> - rsync without the jar name as folder
> - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated)
> use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools":
> - there is a SpringBoot app deployed on OpenShift
> - the developer want to develop evolution of the SpringBoot app
> -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance
> -- Remote java debug should be available when the OpenShift server adapter is in debug mode.
> Steps:
> # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot)
> # EXEC: Import project within fuse-on-openshift.zip into your workspace
> # EXEC: open launch configuration and change:
> ** -Dkubernetes.master= so that it first your cdk instance
> ** -Dkubernetes.namespace= to the name of the project that you create in step 1.
> # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk)
> # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running.
> # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service)
> # ASSERT: server adapter is created and is *[started]*
> # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service)
> # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end
> {code}
> simple-route - >>> 455
> simple-route - >>> 695
> simple-route - >>> 935
> {code}
> # EXEC: In Project Explorer: open class MyTransformer and change the transform method
> # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25508) Properties: should display secrets
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-25508:
----------------------------------------
Summary: Properties: should display secrets
Key: JBIDE-25508
URL: https://issues.jboss.org/browse/JBIDE-25508
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.5.2.AM2
Reporter: Andre Dietisheim
The properties for OpenShift resources dont show "secrets". In oc one can display those via
{code}
oc get secret
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months