[JIRA] (JENKINS-60947) non-VPC spot slaves cant be started
Title: Message Title Vladislav Naumov created an issue Jenkins / JENKINS-60947 non-VPC spot slaves cant be started Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-02-03 08:34 Environment: Jenkins from Ubuntu package, ec2 plugin 1.46 ... 1.49.1 Priority: Major Reporter: Vladislav Naumov looks like this https://issues.jenkins-ci.org/browse/JENKINS-58578 broke non-vpc spot slaves. no matter if "Associate Public IP" checkbox is set or not, slave fails to launch. Theres "The AssociatePublicIpAddress parameter is only supported for VPC launches" message in logfile. Add Comment
[JIRA] (JENKINS-58578) Public IP can still be assigned when Associate Public IP is disabled, depending on subnet(s)
Title: Message Title Vladislav Naumov commented on JENKINS-58578 Re: Public IP can still be assigned when Associate Public IP is disabled, depending on subnet(s) Problem persists in 1.48, non-VPC slaves can't be launched with same "The AssociatePublicIpAddress parameter is only supported for VPC launches" error message. Checkbox does nothing. 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.200731.1563593184000.2374.157950309%40Atlassian.JIRA.
[JIRA] (JENKINS-58578) Public IP can still be assigned when Associate Public IP is disabled, depending on subnet(s)
Title: Message Title Vladislav Naumov commented on JENKINS-58578 Re: Public IP can still be assigned when Associate Public IP is disabled, depending on subnet(s) Looks like this patch breaks non-VPC slaves: no matter if "Associate Public IP" checkbox is set or not, slave fails to launch. Theres "The AssociatePublicIpAddress parameter is only supported for VPC launches" message in logfile. Reverting 1.46.1 -> 1.45 fixes the behavior. 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.200731.1563593184000.9467.157500227%40Atlassian.JIRA.
[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed
Title: Message Title Vladislav Naumov commented on JENKINS-55618 Re: When using spot instances, requests 3-4 nodes when one is needed > If I change the version to 1.40,would the spot instance work fine? Try rolling back to 1.41 first. It worked fine for me. But then again, 1.43 works for me, too. 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.196789.1547639731000.14895.1559125620644%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed
Title: Message Title Vladislav Naumov commented on JENKINS-55618 Re: When using spot instances, requests 3-4 nodes when one is needed > how long takes your node to be ready for use ? Up to a minute with Spot instances. It used to be much worse few years ago – it could take up to 5 minutes back then. Most of this time is spent in that marketplace – on-demand instance comes up 2-3x times faster from same AMI. 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.196789.1547639731000.13345.1559032920392%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed
Title: Message Title Vladislav Naumov commented on JENKINS-55618 Re: When using spot instances, requests 3-4 nodes when one is needed Seems to be fixed in 1.43 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.196789.1547639731000.9943.1558613760351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed
Title: Message Title
Vladislav Naumov created an issue
Jenkins / JENKINS-55618
When using spot instances, requests 3-4 nodes when one is needed
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-01-16 11:55
Labels:
spot
Priority:
Major
Reporter:
Vladislav Naumov
When it is time to request a worker node, more than one can be requested. It requests one, then rapidly checks for if its up (node needs a minute or so to come up when using spot instances), and fires another one, then another – until one of spots is finally there on time. This one becomes Jenkins slave, rest linger there until Spot Marketplace kills it. Seems to be 1.42 specific: I reverted to version 1.41 and it seems to work fine. This is how it looks in Jenkins log file: (notice really short delays, only sir-bd78adpq gets into Jenkins slave list) Jan 15, 2019 2:17:40 PM hudson.plugins.ec2.SlaveTemplate provisionSpot INFO: Spot instance id in provision: sir-dvfib1pn Jan 15, 2019 2:17:40 PM hudson.plugins.ec2.EC2Cloud provision INFO: SlaveTemplate {ami='ami-X', labels=''}. Attempting provision finished, excess workload: 0 Jan 15, 2019 2:17:40 PM hudson.plugins.ec2.EC2Cloud provision INFO: We have now 1 computers, waiting for 1 more Jan 15, 2019 2:17:40 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning current_ami (ami-X) from ec2-ec2 cloud with 1 executors. Remaining excess workload: 0 Jan 15, 2019 2:17:40 PM hudson.plugins.ec2.EC2Cloud$1 call WARNING: SlaveTemplate{ami='ami-X', labels=''} . Node terminated is neither pending, neither running, its {2}. Terminate provisioning Jan 15, 2019 2:17:48 PM hudson.plugins.ec2.EC2Cloud provision INFO: SlaveTemplate{ami='ami-X', labels=''}. Attempting to provision slave needed by
