[JIRA] (JENKINS-50142) Unable to launch slave in AWS due to " Security groups must all be VPC security groups to work in a VPC context"

[vikasbodke@gmail.com (JIRA)]

Vikas Bodke created an issue

Jenkins / JENKINS-50142 Unable to launch slave in AWS due to " Security groups must all be VPC security groups to work in a VPC context" Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2018-03-13 13:12 Labels: AWS ec2-plugin Priority: Major Reporter: Vikas Bodke Hi,   Providing a single security group name/id & single subnet id, both under same VPC gives the error. com.amazonaws.AmazonClientException: Security groups must all be VPC security groups to work in a VPC context at hudson.plugins.ec2.SlaveTemplate.getEc2SecurityGroups(SlaveTemplate.java:986) at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:527) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:407) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:534) at hudson.plugins.ec2.EC2Cloud.doProvision(EC2Cloud.java:340) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) The launch happens when no security group is specified. Eliminating any permission related issue. However as the slave assumes the default security group, which is not the desirable state.  I get the same error when a different vpc security group name/id is specified.   Jenkins Version: 2.111 EC2 Pluging : 1.39   Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[cyrilburd@gmail.com (JIRA)]

Cyril Burd commented on JENKINS-50142

Re: Unable to launch slave in AWS due to " Security groups must all be VPC security groups to work in a VPC context" I had the same issue with one of our security groups. Try to run aws ec2 describe-security-groups --group-ids sg-77777777 In my case, there was a trailing white-space in GroupName. Hope it helps.

Add Comment