EC2- Keeps sending stop signal to a manually stopped instance

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • Component/s: ec2-plugin
    • Environment:
      * Jenkins 2.19.4.2
      * Java Version: 1.8.0_111
      * ec2:1.36 'Amazon EC2 plugin'

      When using EC2 plugin to stop (not terminate) slave instances after a certain amount of idle time, if you stop manually one of those slaves before the stop signal is sent, you can see in the logs messages like the following one:

      INFO	h.p.ec2.EC2RetentionStrategy#internalCheck: Idle timeout of [XXX] after 82 idle minutes
      INFO	h.plugins.ec2.EC2AbstractSlave#idleTimeout: EC2 instance idle time expired: [XXX-ID]
      INFO	h.plugins.ec2.EC2AbstractSlave#stop: EC2 instance stop request sent for [XXX-ID]
      

      The plugin keeps sending the stop signal even if the instance is already stopped.
      This message fill the logs. Any way to remove it?

            Assignee:
            Francis Upton
            Reporter:
            Manuel Cardenas
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: