Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-24876

Server adapter: server adapter for nodejs initially fails, fails to find pods

    Details

    • Sprint:
      devex #136 August 2017
    • Story Points:
      8
    • Steps to Reproduce:
      Hide
      1. 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)
      2. ASSERT: build is running, no pods exist yet
      3. EXEC: create a server adapter for the nodejs-mongo-persistent service
      4. ASSERT: server adapter is created and is "[starting]"

      Result:
      starting fails with the following error:

      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)
      

      This error was initially found by QE in https://github.com/jbosstools/jbosstools-openshift/pull/1518#issuecomment-314738165
      The following screencast shows the error: https://youtu.be/m_bc7K29_NI

      Show
      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: 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) This error was initially found by QE in https://github.com/jbosstools/jbosstools-openshift/pull/1518#issuecomment-314738165 The following screencast shows the error: https://youtu.be/m_bc7K29_NI
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      once the server adapter failed to start with the error, simply restart it again once the build is finished. It will succeed and start syncing.

      Show
      once the server adapter failed to start with the error, simply restart it again once the build is finished. It will succeed and start syncing.
    • Release Notes Text:
      merged into master

      Gliffy Diagrams

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                adietish André Dietisheim
                Reporter:
                adietish André Dietisheim
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: