-
Notifications
You must be signed in to change notification settings - Fork 397
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
aws_kms integration tests unstable #433
Comments
Files identified in the description: If these files are inaccurate, please update the |
ansibullbot
added
bug
This issue/PR relates to a bug
module
module
needs_triage
plugins
plugin (any type)
labels
Feb 21, 2021
jatorcasso
added
backport-3
PR should be backported to the stable-3 branch
and removed
backport-3
PR should be backported to the stable-3 branch
labels
May 6, 2022
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
May 7, 2022
aws_kms - stabilize integration tests SUMMARY Integration tests for this test suite were failing occasionally due to timing issues when waiting for < 45 seconds after updates. Increased the wait times to 45 seconds and split into different tests to run in parallel. Fixes #433 ISSUE TYPE Bugfix Pull Request COMPONENT NAME aws_kms Reviewed-by: Jill R <None> Reviewed-by: Markus Bergholz <[email protected]>
patchback bot
pushed a commit
that referenced
this issue
May 7, 2022
aws_kms - stabilize integration tests SUMMARY Integration tests for this test suite were failing occasionally due to timing issues when waiting for < 45 seconds after updates. Increased the wait times to 45 seconds and split into different tests to run in parallel. Fixes #433 ISSUE TYPE Bugfix Pull Request COMPONENT NAME aws_kms Reviewed-by: Jill R <None> Reviewed-by: Markus Bergholz <[email protected]> (cherry picked from commit cda4830)
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
May 9, 2022
[PR #1112/cda48303 backport][stable-3] aws_kms - stabilize integration tests This is a backport of PR #1112 as merged into main (cda4830). SUMMARY Integration tests for this test suite were failing occasionally due to timing issues when waiting for < 45 seconds after updates. Increased the wait times to 45 seconds and split into different tests to run in parallel. Fixes #433 ISSUE TYPE Bugfix Pull Request COMPONENT NAME aws_kms Reviewed-by: Alina Buzachis <None>
alinabuzachis
added a commit
to alinabuzachis/community.aws
that referenced
this issue
May 25, 2022
…sible-collections#433) ec2_instance - Support throughtput parameter for GP3 volume types SUMMARY ec2_instance - Support throughput parameter for GP3 volume types Fixes ansible-collections#395 ISSUE TYPE Feature Pull Request COMPONENT NAME ec2_instance Reviewed-by: Markus Bergholz <[email protected]> Reviewed-by: Mark Chappell <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: Jill R <None> Reviewed-by: None <None>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
The aws_kms integration tests appear somewhat flaky, this mostly looks like it's due to 'eventual consistency' race conditions, with incorrect 'changed' results, and _info information that seems to be missing the previous change.
aws_kms may need waiters adding.
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
CI
CONFIGURATION
CI
OS / ENVIRONMENT
CI
STEPS TO REPRODUCE
Trigger integration test suites
EXPECTED RESULTS
tests consistently pass
ACTUAL RESULTS
Tests sporadically fail with errors like:
The text was updated successfully, but these errors were encountered: