Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-61789

Agent nodes marked as 'offline' are not terminated when they have been idle beyond the idle termination time setting

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • ec2-plugin
    • None
    • OS: Amazon Linux 2
      Java version: 1.8.0_242
      Plugins:
      - Amazon EC2 plugin 1.49.1
      - Amazon ECR plugin 1.6

      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 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.

       

            mramonleon Ramon Leon
            john2x John Del Rosario
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: