[JIRA] (JENKINS-61789) Agent nodes marked as 'offline' are not terminated when they have been idle beyond the idle termination time setting

[john2x+jenkins.io@gmail.com (JIRA)]

John Del Rosario created an issue

Jenkins / JENKINS-61789 Agent nodes marked as 'offline' are not terminated when they have been idle beyond the idle termination time setting Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-04-02 21:13 Environment: OS: Amazon Linux 2 Java version: 1.8.0_242 Plugins: - Amazon EC2 plugin 1.49.1 - Amazon ECR plugin 1.6 Priority: Minor Reporter: John Del Rosario We have set our agents to terminate after being idle for 30 minutes under the  We also have "Free Space Threshold" enabled under "Preventive Node Monitoring", to automatically mark agents as offline that fall under the threshold. We treat our agents as cattle, so ideally agents that are marked as offline would eventually terminate after being idle for 30 minutes. But that doesn't seem to be the case when both features are enabled. It seems that agents that are marked offline are being ignored by the idle termination check and are left running indefinitely.   Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[john2x+jenkins.io@gmail.com (JIRA)]

John Del Rosario updated an issue

Jenkins / JENKINS-61789 Agent nodes marked as 'offline' are not terminated when they have been idle beyond the idle termination time setting

Change By: John Del Rosario We have set our agents to terminate after being idle for 30 minutes under the   EC2 plugin settings page.

We also have "Free Space Threshold" enabled under "Preventive Node Monitoring", to automatically mark agents as offline that fall under the threshold. We treat our agents as cattle, so ideally agents that are marked as offline would eventually terminate after being idle for 30 minutes. But that doesn't seem to be the case when both features are enabled. It seems that agents that are marked offline are being ignored by the idle termination check and are left running indefinitely.

Add Comment

[john2x+jenkins.io@gmail.com (JIRA)]

John Del Rosario updated an issue

Jenkins / JENKINS-61789 Agent nodes marked as 'offline' are not terminated when they have been idle beyond the idle termination time setting Change By: John Del Rosario

We have set our agents to terminate after being idle for 30 minutes under the EC2 plugin settings page.

We also have "Free Space Threshold" enabled under "Preventive Node Monitoring", to automatically mark agents as offline that whose disks fall under the threshold.

We treat our agents as cattle, so ideally agents that are marked as offline would eventually terminate after being idle for 30 minutes. But that doesn't seem to be the case when both features are enabled. It seems that agents that are marked offline are being ignored by the idle termination check and are left running indefinitely.

Add Comment