-
Notifications
You must be signed in to change notification settings - Fork 690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JENKINS-59562] Always use network interface for subnet #402
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look fine. Do you have any way to test this?
I can test this manually on monday, I'm hoping the issue reporter would test this as well as I have updated the ticket. |
Apparently security groups must be specified the same way as well. Changed that bit too |
CI failures are due to a windows deletion issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have that much knowledge but code looks good.
Hey, will 1.46.1 be released in the plugin repository so we can have it working? |
@kern3l it should be available already. |
If you specify network interfaces you must not specify the subnet or security groups on the instance level.
Essentially what happens is when you specify a network interface all networking related configurations must be on the interface specification or the ec2 api will return an error.