It finally fails with an error like below after ~12 hours: Suppressed: software.amazon.awssdk.core.exception.SdkClientException: Request attempt 16 failure: Request has expired. (Service: Ec2, Status Code: 400, Request ID: xxxxxxxxxxxxxxxxxxxxxxxxxx) On Thursday, June 19, 2025 at 7:00:15 PM UTC+5:30 Abhijeet Ghosh wrote:
> Hi there, > > I am observing an issue related to Jenkins ec2 plugin's latest version, > specifically in all version post 1881.vc14132ea_f042. Please see the > details below: > > *Problem:* > > In the latest Jenkins EC2 plugin versions that utilizes AWS SDK v2, agent > provisioning fails after approximately 12 hours of continuous Jenkins > master uptime when running inside a Kubernetes pod. Initially, agent > launches function correctly post-deployment, but after around 12 hours, no > new agents can be launched until the Jenkins pod is restarted. > > This behaviour is not observed in earlier EC2 plugin versions that use AWS > SDK v1, indicating a possible cause may be related to the migration to AWS > SDK v2. > > *Impact:* > > - Agent provisioning stops working after about 12 hours without > visible errors in the Jenkins UI. > - Restarting the Jenkins pod temporarily resolves the issue by > resetting connections. > > *Request:* > > - Please check if this is something that I am only observing and > suggest a possible resolution. > - In case if others are also facing this issue, is there a resolution > that is planned? > > *Environment Details:* > > - Jenkins EC2 plugin version: 1935.v9b_77210472b_1 > - Jenkins version: 2.504.1 running in a k8s pod > > > Thanks & Regards > Abhijeet Ghosh > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-users/f0193b72-9b93-4706-b020-c1577c9f07f9n%40googlegroups.com.
