[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Tao Yang closed an issue as Fixed Jenkins / JENKINS-55639 ec2-plugin only attempts to retrieve spot instance using old id Change By: Tao Yang Status: Open Closed Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.5065.1558318261088%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Tao Yang commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id Thanks FABRIZIO MANFREDI, it looks to me like it's working correctly now! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.5047.1558318200365%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Paul P commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id I can confirm 1.43 & 2.177 work fine with Spot instances 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.4630.1558125420595%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Yan Corneille commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id Actully I can't, I'm sorry. I had to rollback and fix my instance EC2 plugin to v1.39 due to https://issues.jenkins-ci.org/browse/JENKINS-52362. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.708.1558085040609%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title FABRIZIO MANFREDI edited a comment on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id The 1.43 contains a fix on the missing default value of the new options that are not present for people that come from old plugin. Can you test ? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.690.1558084501554%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id The 1.43 contains a fix on the missing default value of the new options that are not present for people that come from old plugin. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.656.1558084440505%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Paul P edited a comment on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id EDIT: Looks like I spoke too soon, the problem re-appeared.I had this issue and uninstalling the plugin and re-installing it fixed it.To be specific: # backup your config.xml # uninstall the plugin # restart jenkins # re-install the plugin (I lost my configuration) # stop jenkins # replace the config.xml # start JenkinsI am using Jenkins 2.176 and ec2 plugin 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.20483.1557267780450%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Paul P commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id I had this issue and uninstalling the plugin and re-installing it fixed it. To be specific: backup your config.xml uninstall the plugin restart jenkins re-install the plugin (I lost my configuration) stop jenkins replace the config.xml start Jenkins I am using Jenkins 2.176 and ec2 plugin 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.20461.1557264600401%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Victor Chavez edited a comment on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id On Jenkins 2.150.2 EC2 plugin 1.42 we get this behavior intermittently. We oscillate between this and JENKINS-6. 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-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Victor Chavez commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id On 1.42 we get this behavior intermittently. We oscillate between this and JENKINS-6. 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-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Mike Alberghini commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id We also faced this problem on Jenkins 2.157 with ec2-plugin 1.42. Switching our spot instances to regular did not fix the issue, but downgrading the plugin to 1.41 did 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-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title
Tao Yang updated an issue
Jenkins / JENKINS-55639
ec2-plugin only attempts to retrieve spot instance using old id
Change By:
Tao Yang
When Jenkins attempts to provision spot instances, after spot requests are created (incorrectly, as per JENKINS-55618) Jenkins will try to retrieve the spot instance based on the last working instance id from before we upgraded the plugin was upgraded , instead of the instance id returned by the spot request. {code:java}INFO: Spot instance id in provision: sir-34si4rxjINFO: Spot instance id in provision: sir-34si4rxjJan 17, 2019 4:32:10 AM hudson.plugins.ec2.CloudHelper getInstanceINFO: Unexpected number of reservations reported by EC2 for instance id 'i-0b934d05d88272fc4', expected 1 result, found []. Instance seems to be dead.Jan 17, 2019 4:32:10 AM hudson.plugins.ec2.EC2Cloud provisionWARNING: SlaveTemplate{ami='ami-09009aeca3492b598', labels='agent linux'}. Exception during provisioningcom.amazonaws.AmazonClientException: Unexpected number of reservations reported by EC2 for instance id 'i-0b934d05d88272fc4', expected 1 result, found []. Instance seems to be dead. at hudson.plugins.ec2.CloudHelper.getInstance(CloudHelper.java:54) at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(CloudHelper.java:25) at hudson.plugins.ec2.EC2AbstractSlave.fetchLiveInstanceData(EC2AbstractSlave.java:499) at hudson.plugins.ec2.EC2AbstractSlave.(EC2AbstractSlave.java:159) at hudson.plugins.ec2.EC2SpotSlave.(EC2SpotSlave.java:44) at hudson.plugins.ec2.EC2SpotSlave.(EC2SpotSlave.java:37) at hudson.plugins.ec2.SlaveTemplate.newSpotSlave(SlaveTemplate.java:979) at hudson.plugins.ec2.SlaveTemplate.provisionSpot(SlaveTemplate.java:919) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:464) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:578) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:594) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}This hasn't happened with on-demand instances.This may be
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title
Tao Yang created an issue
Jenkins / JENKINS-55639
ec2-plugin only attempts to retrieve spot instance using old id
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-01-17 05:20
Environment:
Jenkins 2.150.2 ec2-plugin 1.42
Priority:
Blocker
Reporter:
Tao Yang
When Jenkins attempts to provision spot instances, after spot requests are created (incorrectly, as per JENKINS-55618) Jenkins will try to retrieve the spot instance based on the last working instance id from before the plugin was upgraded, instead of the instance id returned by the spot request.
INFO: Spot instance id in provision: sir-34si4rxjINFO: Spot instance id in provision: sir-34si4rxjJan 17, 2019 4:32:10 AM hudson.plugins.ec2.CloudHelper getInstanceINFO: Unexpected number of reservations reported by EC2 for instance id 'i-0b934d05d88272fc4', expected 1 result, found []. Instance seems to be dead.Jan 17, 2019 4:32:10 AM hudson.plugins.ec2.EC2Cloud provisionWARNING: SlaveTemplate{ami='ami-09009aeca3492b598', labels='agent linux'}. Exception during provisioningcom.amazonaws.AmazonClientException: Unexpected number of reservations reported by EC2 for instance id 'i-0b934d05d88272fc4', expected 1 result, found []. Instance seems to be dead. at hudson.plugins.ec2.CloudHelper.getInstance(CloudHelper.java:54) at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(CloudHelper.java:25) at hudson.plugins.ec2.EC2AbstractSlave.fetchLiveInstanceData(EC2AbstractSlave.java:499) at hudson.plugins.ec2.EC2AbstractSlave.(EC2AbstractSlave.java:159) at
