[JENKINS-76151] Continuous attempts to connect to the stopped instance

[jenkins-infra-bot]

My usual flow is to launch EC2 instance, run some jobs, and then stop it after idle timeout, not terminate. This allows to run next builds faster because all the dependencies are already downloaded. So when next job appears instance is launched, build is run, and then stopped again.

With the latest plugin (2034.v0a_11fb_792b_ee) instance is launched, job is run and instance is stopped after idle timeout, but then it changes its status to "launching..." and stays like this forever, new jobs are not accepted. In EC2 instance stays in Stopped state. Maybe this change in last build has something to do with this behavior - #1142

Logs from jenkins:

Sep 25, 2025 12:21:02 PM INFO hudson.plugins.ec2.EC2RetentionStrategy internalCheck
Idle timeout of EC2 (EC2 Nodes) - Ubuntu 24.04 with 66Gb disk and 16Gb swap on it (i-0aa5d718ff507ba1c) after 1 idle minutes, instance statusRUNNING
Sep 25, 2025 12:21:02 PM INFO hudson.plugins.ec2.EC2AbstractSlave idleTimeout
EC2 instance idle time expired: i-0aa5d718ff507ba1c
Sep 25, 2025 12:21:03 PM INFO hudson.plugins.ec2.EC2AbstractSlave stop
EC2 instance stop request sent for i-0aa5d718ff507ba1c
Sep 25, 2025 12:22:03 PM WARNING hudson.plugins.ec2.EC2RetentionStrategy attemptReconnectIfOffline
EC2Computer EC2 (EC2 Nodes) - Ubuntu 24.04 with 66Gb disk and 16Gb swap on it (i-0aa5d718ff507ba1c) is offline
Sep 25, 2025 12:22:03 PM WARNING hudson.plugins.ec2.EC2RetentionStrategy attemptReconnectIfOffline
Attempting to reconnect EC2Computer EC2 (EC2 Nodes) - Ubuntu 24.04 with 66Gb disk and 16Gb swap on it (i-0aa5d718ff507ba1c)
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
Launching instance: i-0aa5d718ff507ba1c
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
bootstrap()
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
Getting keypair...
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
Using private key devops-key-pair (SHA-1 fingerprint xxx)
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
Authenticating as ubuntu
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
Connecting to 10.131.100.147 on port 22, with timeout 10000.
Sep 25, 2025 12:22:17 PM INFO hudson.plugins.ec2.EC2Cloud log
Failed to connect via ssh: DefaultConnectFuture[ubuntu@/10.131.100.147:22]: Failed (NoRouteToHostException) to execute: No route to host
Sep 25, 2025 12:22:17 PM INFO hudson.plugins.ec2.EC2Cloud log
Waiting for SSH to come up. Sleeping 5.
Sep 25, 2025 12:22:22 PM INFO hudson.plugins.ec2.EC2Cloud log
Connecting to 10.131.100.147 on port 22, with timeout 10000.
Sep 25, 2025 12:22:25 PM INFO hudson.plugins.ec2.EC2Cloud log
Failed to connect via ssh: DefaultConnectFuture[ubuntu@/10.131.100.147:22]: Failed (NoRouteToHostException) to execute: No route to host
Sep 25, 2025 12:22:25 PM INFO hudson.plugins.ec2.EC2Cloud log
Waiting for SSH to come up. Sleeping 5.
Sep 25, 2025 12:22:30 PM INFO hudson.plugins.ec2.EC2Cloud log
Connecting to 10.131.100.147 on port 22, with timeout 10000.
Sep 25, 2025 12:22:33 PM INFO hudson.plugins.ec2.EC2Cloud log
Failed to connect via ssh: DefaultConnectFuture[ubuntu@/10.131.100.147:22]: Failed (NoRouteToHostException) to execute: No route to host
Sep 25, 2025 12:22:33 PM INFO hudson.plugins.ec2.EC2Cloud log
Waiting for SSH to come up. Sleeping 5.
Sep 25, 2025 12:22:38 PM INFO hudson.plugins.ec2.EC2Cloud log
Connecting to 10.131.100.147 on port 22, with timeout 10000.
Sep 25, 2025 12:22:42 PM INFO hudson.plugins.ec2.EC2Cloud log
Failed to connect via ssh: DefaultConnectFuture[ubuntu@/10.131.100.147:22]: Failed (NoRouteToHostException) to execute: No route to host
Sep 25, 2025 12:22:42 PM INFO hudson.plugins.ec2.EC2Cloud log
Waiting for SSH to come up. Sleeping 5.

Continues like this forever...

---

Originally reported by shohou, imported from: Continuous attempts to connect to the stopped instance

• assignee: jgarciacloudbees
• status: In Review
• priority: Major
• component(s): ec2-plugin
• resolution: Unresolved
• votes: 5
• watchers: 9
• imported: 2025-12-06

Raw content of original issue

My usual flow is to launch EC2 instance, run some jobs, and then stop it after idle timeout, not terminate. This allows to run next builds faster because all the dependencies are already downloaded. So when next job appears instance is launched, build is run, and then stopped again.

With the latest plugin (2034.v0a_11fb_792b_ee) instance is launched, job is run and instance is stopped after idle timeout, but then it changes its status to "launching..." and stays like this forever, new jobs are not accepted. In EC2 instance stays in Stopped state. Maybe this change in last build has something to do with this behavior - #1142

Logs from jenkins:

Sep 25, 2025 12:21:02 PM INFO hudson.plugins.ec2.EC2RetentionStrategy internalCheck
Idle timeout of EC2 (EC2 Nodes) - Ubuntu 24.04 with 66Gb disk and 16Gb swap on it (i-0aa5d718ff507ba1c) after 1 idle minutes, instance statusRUNNING
Sep 25, 2025 12:21:02 PM INFO hudson.plugins.ec2.EC2AbstractSlave idleTimeout
EC2 instance idle time expired: i-0aa5d718ff507ba1c
Sep 25, 2025 12:21:03 PM INFO hudson.plugins.ec2.EC2AbstractSlave stop
EC2 instance stop request sent for i-0aa5d718ff507ba1c
Sep 25, 2025 12:22:03 PM WARNING hudson.plugins.ec2.EC2RetentionStrategy attemptReconnectIfOffline
EC2Computer EC2 (EC2 Nodes) - Ubuntu 24.04 with 66Gb disk and 16Gb swap on it (i-0aa5d718ff507ba1c) is offline
Sep 25, 2025 12:22:03 PM WARNING hudson.plugins.ec2.EC2RetentionStrategy attemptReconnectIfOffline
Attempting to reconnect EC2Computer EC2 (EC2 Nodes) - Ubuntu 24.04 with 66Gb disk and 16Gb swap on it (i-0aa5d718ff507ba1c)
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
Launching instance: i-0aa5d718ff507ba1c
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
bootstrap()
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
Getting keypair...
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
Using private key devops-key-pair (SHA-1 fingerprint xxx)
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
Authenticating as ubuntu
Sep 25, 2025 12:22:03 PM INFO hudson.plugins.ec2.EC2Cloud log
Connecting to 10.131.100.147 on port 22, with timeout 10000.
Sep 25, 2025 12:22:17 PM INFO hudson.plugins.ec2.EC2Cloud log
Failed to connect via ssh: DefaultConnectFuture[ubuntu@/10.131.100.147:22]: Failed (NoRouteToHostException) to execute: No route to host
Sep 25, 2025 12:22:17 PM INFO hudson.plugins.ec2.EC2Cloud log
Waiting for SSH to come up. Sleeping 5.
Sep 25, 2025 12:22:22 PM INFO hudson.plugins.ec2.EC2Cloud log
Connecting to 10.131.100.147 on port 22, with timeout 10000.
Sep 25, 2025 12:22:25 PM INFO hudson.plugins.ec2.EC2Cloud log
Failed to connect via ssh: DefaultConnectFuture[ubuntu@/10.131.100.147:22]: Failed (NoRouteToHostException) to execute: No route to host
Sep 25, 2025 12:22:25 PM INFO hudson.plugins.ec2.EC2Cloud log
Waiting for SSH to come up. Sleeping 5.
Sep 25, 2025 12:22:30 PM INFO hudson.plugins.ec2.EC2Cloud log
Connecting to 10.131.100.147 on port 22, with timeout 10000.
Sep 25, 2025 12:22:33 PM INFO hudson.plugins.ec2.EC2Cloud log
Failed to connect via ssh: DefaultConnectFuture[ubuntu@/10.131.100.147:22]: Failed (NoRouteToHostException) to execute: No route to host
Sep 25, 2025 12:22:33 PM INFO hudson.plugins.ec2.EC2Cloud log
Waiting for SSH to come up. Sleeping 5.
Sep 25, 2025 12:22:38 PM INFO hudson.plugins.ec2.EC2Cloud log
Connecting to 10.131.100.147 on port 22, with timeout 10000.
Sep 25, 2025 12:22:42 PM INFO hudson.plugins.ec2.EC2Cloud log
Failed to connect via ssh: DefaultConnectFuture[ubuntu@/10.131.100.147:22]: Failed (NoRouteToHostException) to execute: No route to host
Sep 25, 2025 12:22:42 PM INFO hudson.plugins.ec2.EC2Cloud log
Waiting for SSH to come up. Sleeping 5.

Continues like this forever...

environment

Jenkins 2.516.3<br/>
Amazon EC2 Plugin 2034.v0a_11fb_792b_ee

[jenkins-infra-bot]

• Remote link associated with this issue:

  • GH Pull Request

[jenkins-infra-bot]

mlink:

• Comment link
• Original comment link (no redirect)
• Raw content of original comment:

  We hit this issue as well. Confirmed that 
  2032.v92a_4b_e703974 works correctly.
  

We hit this issue as well. Confirmed that
2032.v92a_4b_e703974 works correctly.

[jenkins-infra-bot]

carlos_ponte:

• Comment link
• Original comment link (no redirect)
• Raw content of original comment:

  We have tried downgrading to 2032.v92a_4b_e703974 and it has started working for us as well.
  
  Thanks a lot mlink!
  

We have tried downgrading to 2032.v92a_4b_e703974 and it has started working for us as well.

Thanks a lot mlink!

[jenkins-infra-bot]

mwebber:

• Comment link
• Original comment link (no redirect)
• Raw content of original comment:

  This was apparently fixed in release 2039.v829e6272107c, but when I tested that release I found the opposite problem - agents would never start. See JENKINS-76200.
  

This was apparently fixed in release 2039.v829e6272107c, but when I tested that release I found the opposite problem - agents would never start. See JENKINS-76200.