• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • amazon-ecs-plugin
    • None

      As part of a demo I have created an EC2 Jenkins instance and hooked it up to an ECS cloud with the Amazon EC2 Container Service plugin. They are both on the same VPC and subnet and I have confirmed that the Jenkins Master can see the slaves.

      When I provision the container slaves in ECS they show up as nodes in Jenkins, but they are all down. When I go to configure them I get the following stack error

      org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.60.2.jar!/hudson/model/Computer/configure.jelly:43:71: <st:include> No page found 'configure-entries.jelly' for class com.cloudbees.jenkins.plugins.amazonecs.ECSSlave

      The logs make it look like they are struggling to provision the nodes. I see the following error over and over:

      Unexpected exception encountered while provisioning agent ECS Slave ecs
      java.lang.IllegalStateException: ECS Slave ecs-slave-nodes-18a5b5a727cb7 (ecs task arn:aws:ecs:us-east-1:858585593831:task/dc2f3717-7a61-4360-aca0-fc5e4cfce198) not connected since 7/25/17 5:51 PM seconds
      	at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:282)
      	at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:221)
      	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at java.lang.Thread.run(Thread.java:748)

          [JENKINS-45787] AWS ECS slaves won't stay up

          It seems to be related to this issue here. However I think I have more of the information that you are looking for roehrijn2.

          Vernon Lingley added a comment - It seems to be related to this issue here. However I think I have more of the information that you are looking for roehrijn2 .

          Jason MCDev added a comment -

          I have the same problem.  Nodes come up but never run a job.  No errors on the Jenkins side, or from the docker side.

          When I click on the configuration, Jenkins blows up.  I have been pulling my hair out for days.  An ideas?

          Can I give more info to help?

           

          Jason MCDev added a comment - I have the same problem.  Nodes come up but never run a job.  No errors on the Jenkins side, or from the docker side. When I click on the configuration, Jenkins blows up.  I have been pulling my hair out for days.  An ideas? Can I give more info to help?  

          Vernon Lingley added a comment - - edited

          I was able to get the nodes to launch and execute jobs correctly by moving my Docker image from the public hub.docker.com repo into ECR. I don't think ECS can or wants to access images outside of AWS.

          I still had the above problem though when viewing the nodes.

          Vernon Lingley added a comment - - edited I was able to get the nodes to launch and execute jobs correctly by moving my Docker image from the public hub.docker.com repo into ECR. I don't think ECS can or wants to access images outside of AWS. I still had the above problem though when viewing the nodes.

          Jason MCDev added a comment -

          My issue turned out to be improper permissions.

          Jason MCDev added a comment - My issue turned out to be improper permissions.

          David Potter added a comment -

          jsnmcdev, I'm running into the same issue you were having.  Node comes up, no errors anywhere, but the job doesn't get run, then jenkins blows up when I click configuration.  You say that your issue was permissions related.  Could you please elaborate?  What permissions did you change?

          David Potter added a comment - jsnmcdev , I'm running into the same issue you were having.  Node comes up, no errors anywhere, but the job doesn't get run, then jenkins blows up when I click configuration.  You say that your issue was permissions related.  Could you please elaborate?  What permissions did you change?

          Jady Liu added a comment -

          de1tae1even, I am having the exact same issue, have you got it work yet? 

          Jady Liu added a comment - de1tae1even , I am having the exact same issue, have you got it work yet? 

          Neeraj Malve added a comment -

          Has anyone found the resolution? 

          Neeraj Malve added a comment - Has anyone found the resolution? 

          Vlad Aginsky added a comment -

          similar case here, what permissions were changed to resolve?

          Vlad Aginsky added a comment - similar case here, what permissions were changed to resolve?

            roehrijn2 Jan Roehrich
            vlingley Vernon Lingley
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: