[jbosstools-issues] [JBoss JIRA] (JBIDE-25510) Server adapter: restarting into "Debug" fails on OpenShift Online

Andre Dietisheim (JIRA) issues at jboss.org
Thu Dec 14 05:31:00 EST 2017


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/adietish-stage/deploymentconfigs/wildfly 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/adietish-stage/deploymentconfigs/wildfly 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)


More information about the jbosstools-issues mailing list