-
Notifications
You must be signed in to change notification settings - Fork 398
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
Attempt to improve the stability of ec2_vpc_vgw and ec2_vpc_vpn #162
Attempt to improve the stability of ec2_vpc_vgw and ec2_vpc_vpn #162
Conversation
1c84d22
to
e9acf96
Compare
Migration to wrapped clients has broken the unit tests, will need to dig into those to fix |
Need to fix unit tests to cope with wrapped client |
582f048
to
03902f7
Compare
7a53bcb
to
dfd6390
Compare
@tremble I noticed you took the WIP off this. What you have here looks good, were you still working on the unit tests? |
@jillr Unit tests still need updating, I thought it was done and then realised that the unit tests weren't being run |
…r of mutating objects has been reached'
dfd6390
to
7b440b5
Compare
7b440b5
to
283bbd7
Compare
@jillr ok. Unit tests fixed. (rolls eyes at how stupidly simple the fix was) |
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.
LGTM. Thank you. This also helped me dig deeper into how to use AWSRetry. :-)
Tests passing and approved. Merging |
…ble-collections#162) * Add a custom Retry so we can retry when we receive 'The maximum number of mutating objects has been reached' * Update ec2_vpc_vpn unit test to use a connection with an AWSRetry decorator * changelog
…_vpn (ansible-collections#162) * Add a custom Retry so we can retry when we receive 'The maximum number of mutating objects has been reached' * Update ec2_vpc_vpn unit test to use a connection with an AWSRetry decorator * changelog This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections@79e0928
…ble-collections#162) * Add a custom Retry so we can retry when we receive 'The maximum number of mutating objects has been reached' * Update ec2_vpc_vpn unit test to use a connection with an AWSRetry decorator * changelog
…ble-collections#162) * Add a custom Retry so we can retry when we receive 'The maximum number of mutating objects has been reached' * Update ec2_vpc_vpn unit test to use a connection with an AWSRetry decorator * changelog
…ble-collections#162) * Add a custom Retry so we can retry when we receive 'The maximum number of mutating objects has been reached' * Update ec2_vpc_vpn unit test to use a connection with an AWSRetry decorator * changelog
SUMMARY
With the increased concurrency of tests we've started hitting 'The maximum number of mutating objects has been reached.'
Unfortunately AWS uses the same Error Code for 'Too much changing' as 'Too many VPNs/VGWs', so we need to tweak the retry class a little
fixes: #156
fixes: #154
ISSUE TYPE
COMPONENT NAME
ec2_vpc_vgw
ec2_vpc_vpn
ADDITIONAL INFORMATION
See attached issues for example failures