[JENKINS-76322] Jenkins EC2 plugin version bug 2043.v483cc2854116 teminates instance immediately just after launch

[jenkins-infra-bot]

We have upgraded our jenkins ec2 plugin to this version and then it start producing issues

 

Here is the issue:

Agent is spin up and immediately terminated.

It appeared sdkexcetion is not waiting instnace to get ip address as it lauches in very quick and terminating it. Whereas Version1864.v6fc4480cb_8fb_  version is working perfect.

Appeard issue to be 
Since migreated AmazonClientException   To  SdkException

 

---

Originally reported by nehrusani, imported from: Jenkins EC2 plugin version bug 2043.v483cc2854116 teminates instance immediately just after launch

• assignee: thoulen
• status: Open
• priority: Blocker
• component(s): ec2-plugin
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 2025-12-06

Raw content of original issue

We have upgraded our jenkins ec2 plugin to this version and then it start producing issues

 

Here is the issue:

Agent is spin up and immediately terminated.

It appeared sdkexcetion is not waiting instnace to get ip address as it lauches in very quick and terminating it. Whereas Version1864.v6fc4480cb_8fb_  version is working perfect.

Appeard issue to be 
Since migreated AmazonClientException   To  SdkException

 

2 attachments

• image-2025-12-04-14-13-59-051.png

  

• image-2025-12-04-14-34-41-559.png

  

[jenkins-infra-bot]

markewaite:

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

  Please provide enough details so that others can duplicate the issue.  "How to report an issue" includes a checklist of the type of information to provide.
  

Please provide enough details so that others can duplicate the issue. "How to report an issue" includes a checklist of the type of information to provide.

[jenkins-infra-bot]

JIRAUSER163522:

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

  
  Above connection strategy we tested and also private-dns as well but all are giving same result
  
  Issue is happening to Jenkins agent while agent is being spinned and immediately it is terminated.
  
   
  
  We are running Jenkins in EKS pod and using docker based image of jenkins and using not any proxy.
  
   
  
  Using docker image and using it on EKS platform on a pod
  
  And of jenkins docker image version is:  jenkins/jenkins:2.479.3
  
  EC2 plugin version:           2043.v483cc2854116
  
  
  
   
  
  And in Jenkins build agent as starts and terminated quickly and on logs it says
  
   
  
  
  
   
  
  And previous version of ec2 plugin which was working is:   Version1864.v6fc4480cb_8fb
  
   
  
  And after upgrade jenkins ec2 plugin:  2043.v483cc2854116    issue started occuring
  
   
  
   
  
   
  

Above connection strategy we tested and also private-dns as well but all are giving same result

Issue is happening to Jenkins agent while agent is being spinned and immediately it is terminated.

 

We are running Jenkins in EKS pod and using docker based image of jenkins and using not any proxy.

 

Using docker image and using it on EKS platform on a pod

And of jenkins docker image version is:  jenkins/jenkins:2.479.3

EC2 plugin version:           2043.v483cc2854116

 

And in Jenkins build agent as starts and terminated quickly and on logs it says

 

 

And previous version of ec2 plugin which was working is:   Version1864.v6fc4480cb_8fb

 

And after upgrade jenkins ec2 plugin:  2043.v483cc2854116    issue started occuring