-
Bug
-
Resolution: Not A Defect
-
Major
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
[JENKINS-50141] Unable to launch slave in AWS due to " Security groups must all be VPC security groups to work in a VPC context"
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Closing as this got submitted in error