[jbosstools-issues] [JBoss JIRA] (JBIDE-24876) Server adapter: server adapter for nodejs initially fails, fails to find pods

[Andre Dietisheim (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-24876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-24876:
-------------------------------------
    Steps to Reproduce: 
# EXEC: create a new application based on the *nodejs-mongo-persistent* template (you need to create a fresh one, once the build is running and pods exists, the error wont happen any more)
# ASSERT: build is running, no pods exist yet
# EXEC: create a server adapter for the *nodejs-mongo-persistent* service
# ASSERT: server adapter is created and is "[starting]"

Result:
starting fails with the following error:
 !image-2017-08-17-16-00-23-018.png! 
{code}
org.eclipse.core.runtime.CoreException: Could not find a deployment config for replication controller nodejs-mongo-persistent-1: no pods found.You may have to wait for your build to finish and create your pods.
	at org.jboss.tools.openshift.internal.core.util.ResourceUtils.getDeploymentConfigFor(ResourceUtils.java:983)
	at org.jboss.tools.openshift.internal.core.util.ResourceUtils.getDeploymentConfigFor(ResourceUtils.java:954)
	at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getDeploymentConfig(OpenShiftServerUtils.java:539)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.waitForDeploymentConfigReady(OpenShiftLaunchController.java:123)
	at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:45)
	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 error was initially found by QE in https://github.com/jbosstools/jbosstools-openshift/pull/1518#issuecomment-314738165

  was:
# EXEC: create a new application based on the *nodejs-mongo-persistent* template (you need to create a fresh one, once the build is running and pods exists, the error wont happen any more)
# ASSERT: build is running, no pods exist yet
# EXEC: create a server adapter for the *nodejs-mongo-persistent* service
# ASSERT: server adapter is created and is "[starting]"

Result:
starting fails with the following error:
 !image-2017-08-17-16-00-23-018.png! 
{code}
org.eclipse.core.runtime.CoreException: Could not find a deployment config for replication controller nodejs-mongo-persistent-1: no pods found.You may have to wait for your build to finish and create your pods.
	at org.jboss.tools.openshift.internal.core.util.ResourceUtils.getDeploymentConfigFor(ResourceUtils.java:983)
	at org.jboss.tools.openshift.internal.core.util.ResourceUtils.getDeploymentConfigFor(ResourceUtils.java:954)
	at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getDeploymentConfig(OpenShiftServerUtils.java:539)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.waitForDeploymentConfigReady(OpenShiftLaunchController.java:123)
	at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:45)
	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}



> Server adapter: server adapter for nodejs initially fails, fails to find pods
> -----------------------------------------------------------------------------
>
>                 Key: JBIDE-24876
>                 URL: https://issues.jboss.org/browse/JBIDE-24876
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.5.0.AM1
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>             Fix For: 4.5.1.AM2
>
>         Attachments: image-2017-08-17-16-00-23-018.png
>
>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)