-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Master:
Ubuntu 16.04.2 LTS on Amazon EC2
openjdk version "1.8.0_131"
OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.16.04.2-b11)
OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
Jenkins 2.60.2
EC2 Container Service plugin v1.11
EC2 Plugin v1.36
P4 Plugin v1.72
All other plugins are defaults when the instance was created last Wednesday
Jenkins is accessible directly via the AWS host. There is no revers proxy that I am aware of.Master: Ubuntu 16.04.2 LTS on Amazon EC2 openjdk version "1.8.0_131" OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.16.04.2-b11) OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode) Jenkins 2.60.2 EC2 Container Service plugin v1.11 EC2 Plugin v1.36 P4 Plugin v1.72 All other plugins are defaults when the instance was created last Wednesday Jenkins is accessible directly via the AWS host. There is no revers proxy that I am aware of.
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)
- is related to
-
-
- Reopened
-
[JENKINS-45787] AWS ECS slaves won't stay up
| Link | New: This issue is related to JENKINS-40664 [ JENKINS-40664 ] |
| Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Neeraj Malve
made changes -
| Attachment | New: Screenshot from 2019-08-20 18-24-36.png [ 48373 ] |
