[JIRA] (JENKINS-36516) EC2 plugin: Plugin fails to automatically launch slaves to meet demand
Title: Message Title Ben Copeland commented on JENKINS-36516 Re: EC2 plugin: Plugin fails to automatically launch slaves to meet demand Still an issue in 1.42 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49705) EC2 plugin fails to launch agents after some time.
Title: Message Title Ben Copeland updated an issue Jenkins / JENKINS-49705 EC2 plugin fails to launch agents after some time. Change By: Ben Copeland Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49705) EC2 plugin fails to launch agents after some time.
Title: Message Title Ben Copeland commented on JENKINS-49705 Re: EC2 plugin fails to launch agents after some time. Was this not fixed in JENKINS-26854 ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49705) EC2 plugin fails to launch agents after some time.
Title: Message Title Ben Copeland edited a comment on JENKINS-49705 Re: EC2 plugin fails to launch agents after some time. Was this not fixed in JENKINS-26854 ? I still see problems with EC2 Plugin 1.42 and I have confirmed with AWS support the session is in fact expiring and not being refreshed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48096) EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance
Title: Message Title Ben Copeland commented on JENKINS-48096 Re: EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance Regression from JENKINS-26854 ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48096) EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance
Title: Message Title Ben Copeland commented on JENKINS-48096 Re: EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance After looking closer this seems to be a bug. Was this not "fixed" with issues like JENKINS-36516 I confirmed with AWS support after looking through the session logs the session is in fact expiring and the plug-in is failing to refresh. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48096) EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance
Title: Message Title Ben Copeland updated an issue Jenkins / JENKINS-48096 EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance Change By: Ben Copeland Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48096) EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance
Title: Message Title Ben Copeland commented on JENKINS-48096 Re: EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance This is an issue with us as well. Almost verbatim the same symptoms as described above. I have confirmed with AWS support this is indeed a session timeout. The plugin does not re-auth and refresh the session. Maybe a session refresh interval as a configuration option or something along those lines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49705) EC2 plugin fails to launch agents after some time.
Title: Message Title Ben Copeland edited a comment on JENKINS-49705 Re: EC2 plugin fails to launch agents after some time. I have exactly the same issue here as well. I have confirmed my clocks are correct and synchronized with ntp. The jenkins master just gives up trying to contact the slave, the slave as a result is orphaned, in running state and reachable via SSH from the jenkins master. I am using a VPC peer in AWS. The Jenkins master is in an AWS "infrastructure" account. com.amazonaws.services.ec2.model.AmazonEC2Exception: Request has expired. * [Jenkins ver. 2.150.2|https://jenkins.io/] (running in a docker container) * EC2 Plugin v. 1.39 * AWS SDK Plugin v. 1.11.457this is working with a Jenkins master running similar network setup * Jenkins ver. 2.10 (not in a container) * EC2 Plugin v. 1.35 * AWS SDK plugin 1.10.16 Note: This issue is blocking us from upgrading Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49705) EC2 plugin fails to launch agents after some time.
Title: Message Title Ben Copeland commented on JENKINS-49705 Re: EC2 plugin fails to launch agents after some time. I have exactly the same issue here as well. I have confirmed my clocks are correct and synchronized with ntp. The jenkins master just gives up trying to contact the slave, the slave as a result is orphaned, in running state and reachable via SSH from the jenkins master. I am using a VPC peer in AWS. The Jenkins master is in an AWS "infrastructure" account. com.amazonaws.services.ec2.model.AmazonEC2Exception: Request has expired. Jenkins ver. 2.150.2 (running in a docker container) EC2 Plugin v. 1.39 AWS SDK Plugin v. 1.11.457 this is working with a Jenkins master running similar network setup Jenkins ver. 2.10 (not in a container) EC2 Plugin v. 1.35 AWS SDK plugin 1.10.16 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
