-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
Hi Team,
Currently I have a setup in Jenkins where i am using aws-ec2 plugin to launch new on-demand ec2 instance when job is triggered.
The Termination time is set to 5mins
So when the slave is idle for 5mins, the instance is stopped from AWS end however the jenkins slave is not deleted and the log stays stuck in Killed by signal 15
Last line of Slave logs
connection terminated
channel stopped
killed by signal 15
We have to manually delete the slave every time so that new instance can be created next time when job is triggered.
Kindly help to understand the issue
Regards,
Prem
[JENKINS-66059] Ec2 Slave Termination Long running
Description |
Original:
Hi Team,
Currently I have a setup in Jenkins were i am using aws-ec2 plugin to launch new on-demand ec2 instance when job is triggered. The Termination time is set to 5mins So when the slave is idle for 5mins, the instance is stopped from AWS end however the jenkins slave is not deleted and the log stays stuck in *Killing signal 15* Last line of Slave logs *connection terminated* *channel stopped* *killed by signal 15* We have to manually delete the slave every time so that new instance can be created next time when job is triggered. Kindly help to understand the issue Regards, Prem |
New:
Hi Team,
Currently I have a setup in Jenkins where i am using aws-ec2 plugin to launch new on-demand ec2 instance when job is triggered. The Termination time is set to 5mins So when the slave is idle for 5mins, the instance is stopped from AWS end however the jenkins slave is not deleted and the log stays stuck in *Killing signal 15* Last line of Slave logs *connection terminated* *channel stopped* *killed by signal 15* We have to manually delete the slave every time so that new instance can be created next time when job is triggered. Kindly help to understand the issue Regards, Prem |
Description |
Original:
Hi Team,
Currently I have a setup in Jenkins where i am using aws-ec2 plugin to launch new on-demand ec2 instance when job is triggered. The Termination time is set to 5mins So when the slave is idle for 5mins, the instance is stopped from AWS end however the jenkins slave is not deleted and the log stays stuck in *Killing signal 15* Last line of Slave logs *connection terminated* *channel stopped* *killed by signal 15* We have to manually delete the slave every time so that new instance can be created next time when job is triggered. Kindly help to understand the issue Regards, Prem |
New:
Hi Team,
Currently I have a setup in Jenkins where i am using aws-ec2 plugin to launch new on-demand ec2 instance when job is triggered. The Termination time is set to 5mins So when the slave is idle for 5mins, the instance is stopped from AWS end however the jenkins slave is not deleted and the log stays stuck in *Killed by signal 15* Last line of Slave logs *connection terminated* *channel stopped* *killed by signal 15* We have to manually delete the slave every time so that new instance can be created next time when job is triggered. Kindly help to understand the issue Regards, Prem |