[JIRA] (JENKINS-59661) EC2 fails to provision due incorrect instance cap

[h35...@edu.uwaterloo.ca (JIRA)]

Title: Message Title

Handi Gao commented on JENKINS-59661   Re: EC2 fails to provision due incorrect instance cap ryan M Yeah, the probelm they are having is that the EC2 instance gets restarted in AWS but it will take some time for it to show as "Pending" and the plugin only checks the state of the instance once... if the state is neither running or pending, Jenkins stops provisioning the node... the pr adds the idea of retrying when waking up stopped instances so it should be able to solve the issue we are having right now Oct 16, 2019 5:06:19 PM WARNING hudson.plugins.ec2.EC2Cloud$1 call SlaveTemplate{ami='ami-02eac2c0129f6376b', labels='default master_ec2'}. Node stopped is neither pending, neither running, its {2}. Terminate provisioning For the environment variables, I'm not sure if the init script can add them for you... you could check it out, may save you some effort Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202351.1570203874000.10593.1571414280315%40Atlassian.JIRA.