You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
The Jenkins controller is based off of latest the official Docker Image jenkins/jenkins:2.378
The agents are based off of the latest official Docker Image: jenkins/inbound-agent:3071.v7e9b_0dc08466-1
Due to our Enterprise Architecture, we have slightly modified the actual Images our container are based on. Custom certificates, in-house artifact server, and such stuff.
Reproduction steps
Start a multibranch pipeline job
Wait until it is done.
Verify node has been removed from Jenkins
Verify node still exists in AWS ECS having status RUNNING
Look in the Jenkins log
Expected Results
Log output:
Nov 17, 2022 9:07:06 AM INFO hudson.slaves.CloudRetentionStrategy check
Disconnecting ecs-ecs2-7999w
Nov 17, 2022 9:07:06 AM INFO com.cloudbees.jenkins.plugins.amazonecs.ECSSlave _terminate
[ecs-ecs2-7999w]: Stopping: TaskArn arn:aws:ecs:eu-west-1:912774568938:task/CI-build-agents/e4d3a260d79d45e2b155a5ebe5e28d06, ClusterArn arn:aws:ecs:eu-west-1:912774568938:cluster/CI-build-agents
...
Computer.threadPoolForRemoting [#19] for ecs-ecs2-7999w terminated: java.nio.channels.ClosedChannelException
Actual Results
Log output:
Disconnecting ecs-ecs8-cb764
Nov 17, 2022 9:12:49 AM INFO com.cloudbees.jenkins.plugins.amazonecs.ECSSlave _terminate [ecs-ecs8-cb764]: Stopping: TaskArn ecs-ecs8-cb764, ClusterArn arn:aws:::cluster/
Nov 17, 2022 9:12:49 AM INFO com.cloudbees.jenkins.plugins.amazonecs.ECSService stopTask
Delete ECS agent task: ecs-ecs8-cb764
Nov 17, 2022 9:12:49 AM SEVERE com.cloudbees.jenkins.plugins.amazonecs.ECSService stopTask
Couldn't stop task arn ecs-ecs8-cb764 caught exception: taskId length should be one of [32,36] (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: 9445cd94-93bd-4d43-b94f-7be867fe4f2b; Proxy: null)
com.amazonaws.services.ecs.model.InvalidParameterException: taskId length should be one of [32,36] (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: 9445cd94-93bd-4d43-b94f-7be867fe4f2b; Proxy: null)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1879)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleServiceErrorResponse(AmazonHttpClient.java:1418)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1387)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1157)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:814)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:781)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:755)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:715)
at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:697)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:561)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:541)
at com.amazonaws.services.ecs.AmazonECSClient.doInvoke(AmazonECSClient.java:4691)
at com.amazonaws.services.ecs.AmazonECSClient.invoke(AmazonECSClient.java:4658)
at com.amazonaws.services.ecs.AmazonECSClient.invoke(AmazonECSClient.java:4647)
at com.amazonaws.services.ecs.AmazonECSClient.executeStopTask(AmazonECSClient.java:3447)
at com.amazonaws.services.ecs.AmazonECSClient.stopTask(AmazonECSClient.java:3416)
at com.cloudbees.jenkins.plugins.amazonecs.ECSService.stopTask(ECSService.java:164)
at com.cloudbees.jenkins.plugins.amazonecs.ECSSlave._terminate(ECSSlave.java:146)
at hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:88)
at hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:61)
at hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:45)
at hudson.slaves.ComputerRetentionWork$1.run(ComputerRetentionWork.java:71)
at hudson.model.Queue._withLock(Queue.java:1396)
at hudson.model.Queue.withLock(Queue.java:1270)
at hudson.slaves.ComputerRetentionWork.doRun(ComputerRetentionWork.java:62)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:94)
at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:69)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Nov 17, 2022 9:12:49 AM INFO jenkins.slaves.DefaultJnlpSlaveReceiver channelClosed Computer.threadPoolForRemoting [#99] for ecs-ecs8-cb764 terminated: java.nio.channels.ClosedChannelException
...
[JNLP4-connect connection from /:] Refusing headers from remote: Unknown client name: ecs-ecs8-cb764
...
Anything else?
This does not happen every time. Although it appears very often after upgrading to use plugin version 1.46. We could not replicate the issue with version 1.41.
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
The Jenkins controller is based off of latest the official Docker Image jenkins/jenkins:2.378
The agents are based off of the latest official Docker Image: jenkins/inbound-agent:3071.v7e9b_0dc08466-1
Due to our Enterprise Architecture, we have slightly modified the actual Images our container are based on. Custom certificates, in-house artifact server, and such stuff.
Reproduction steps
RUNNING
Expected Results
Log output:
...
Actual Results
Log output:
...
...
Anything else?
This does not happen every time. Although it appears very often after upgrading to use plugin version 1.46. We could not replicate the issue with version 1.41.
The text was updated successfully, but these errors were encountered: