-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Re-enable ec2_vpc_vpn_facts test #58893
Conversation
Unable to reproduce failure locally, let's see if shippable still fails
@jillr Go ahead and enable them. If they start failing again we can disable and investigate further. |
Fixes: #53185 |
@jillr 👍 Actually closes: #49751. I think the errors in #53185 are a subset of the ones for #49751, but the ec2_vpc_vgw tests themselves are still disabled. If you'd like to re-enable those too, feel free. If you add Just some background on unstable tests since these are tricky and sporadic and painstaking to actually solve - As you noted, the module code and tests can be unchanged and suddenly work great (or conversely, fail all over the place). In most cases the reason the tests are unstable is because many AWS services (like EC2, IAM, and S3) use an eventual consistency model. Because of this the failures can be pretty unpredictable (I'd loop tests to run 50 times and do that several times when trying to fix these bugs to address all the different possible places for failure). AWS seems to occasionally make changes to the model which have caused many widespread failures in tests that have never had a problem before. ec2_vpc_vgw was one of these - it has been disabled a couple times now through no fault of Ansible. Even if the tests don't fail when you run them x times, adding AWSRetry and waiters between API calls made by the module are good preventative measures and make the module more resilient against AWS making changes to their distributed system that supports the API. |
@s-hertel ok cool, that's super useful info - thanks! |
Unable to reproduce failure locally, let's see if shippable still fails
SUMMARY
Test re-enabling ec2_vpc_vpn_facts test.
ISSUE TYPE
COMPONENT NAME
ec2_vpc_vpn_facts integration test
ADDITIONAL INFORMATION
Unable to reproduce timeout failures locally in us-east-1 or us-west-2 though nothing has changed in the test or the module. ¯_(ツ)_/¯