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

Server adapter: timeouts when starting into "Debug" on OpenShift Online

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 4.5.2.Final
    • Fix Version/s: 4.5.3.AM2
    • Component/s: openshift
    • Labels:
      None
    • Sprint:
      devex #145 February 2018

      Description

      1. ASSERT: have an account on OpenShift Online
      2. EXEC: create a new application via template nodejs-mongo-persistent
      3. EXEC: have the project imported into the workspace and the server adapter for it created
      4. ASSERT: you have a new server adapter for your app in state [stopped]
      5. 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:

      In the Eclipse log you'll find the following:

      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)
      

        Gliffy Diagrams

          Attachments

          1. error-waiting-for-new-pod.png
            error-waiting-for-new-pod.png
            77 kB
          2. image-2018-01-24-18-58-29-159.png
            image-2018-01-24-18-58-29-159.png
            128 kB
          3. image-2018-01-25-10-49-09-369.png
            image-2018-01-25-10-49-09-369.png
            40 kB
          4. image-2018-01-26-00-49-39-691.png
            image-2018-01-26-00-49-39-691.png
            55 kB
          5. pod-ports-cdk.png
            pod-ports-cdk.png
            39 kB
          6. pod-ports-online.png
            pod-ports-online.png
            36 kB
          7. port-missing.png
            port-missing.png
            66 kB

            Issue Links

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: