[JIRA] (JENKINS-56435) Spot instance requests use entirely different instance

[richard.bowa...@gmail.com (JIRA)]

Title: Message Title

Richard Bowater created an issue   Jenkins / JENKINS-56435 Spot instance requests use entirely different instance Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-03-06 11:00 Environment: ec2 1.42, jenkins 2.167 Priority: Major Reporter: Richard Bowater Spinning up a build agent template that uses spot pricing appears to use the ID of an instance provisioned by a totally different spot request. e.g.  Spot instance id in provision: sir-d29i7m7m Mar 06, 2019 10:50:36 AM INFO hudson.plugins.ec2.EC2RetentionStrategy start Start requested for jenkins-test-agent (sir-d29i7m7m) Mar 06, 2019 10:50:36 AM INFO hudson.plugins.ec2.EC2Cloud log Launching instance: i-0569a98d4e6447e66 In this example, instance i-0569a98d4e6447e66 is an instance fulfilled by a spot request created 1 hour prior. The spot instance provisioned by sir-d29i7m7m eventually starts but is untracked anywhere by Jenkins. This is incredibly frustrating, because I'm ending up terminating totally unrelated instances because the config cannot be changed once the agent has been created and of course it cannot ssh in to instances created with an entirely different keypair. I'm not sure how to debug this further, so would appreciate any advice in being able to provide more information or if this is a dupe. 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.