Skip to content
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

Use NormalizedOperationMethod to catch ClientErrors in custom waiter #37356

Merged
merged 1 commit into from Mar 13, 2018

Conversation

ryansb
Copy link
Contributor

@ryansb ryansb commented Mar 13, 2018

SUMMARY

Wrap the describe_route_tables call so that ClientError exceptions are caught and error responses can be handled by the error-matchers in custom waiters.

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

ec2_vpc_route_table

ANSIBLE VERSION

ADDITIONAL INFORMATION

@ryansb ryansb requested a review from s-hertel March 13, 2018 16:14
@ansibot ansibot added bug This issue/PR relates to a bug. needs_triage Needs a first human triage before being processed. support:core This issue/PR relates to code supported by the Ansible Engineering Team. labels Mar 13, 2018
@ryansb ryansb removed the needs_triage Needs a first human triage before being processed. label Mar 13, 2018
@s-hertel s-hertel merged commit 93946ba into ansible:devel Mar 13, 2018
@ryansb ryansb deleted the custom-waiter-catch-exception branch March 22, 2018 21:10
s-hertel pushed a commit to s-hertel/ansible that referenced this pull request Apr 27, 2018
s-hertel pushed a commit to s-hertel/ansible that referenced this pull request Apr 27, 2018
s-hertel pushed a commit to s-hertel/ansible that referenced this pull request Apr 27, 2018
s-hertel added a commit that referenced this pull request May 15, 2018
…9171/38960 (#39440)

* [cloud] Make ec2_vpc_route_table wait for the route to propagate (#35975)

* Stabilize ec2_vpc_route_table

Wait for route table to be present before attempting to use it

Sleep before getting the final state of the route table in case modifications are incomplete

* Conditionally wait if changes were made

* Simplify logic

(cherry picked from commit 8fb31ac)

* Route custom waiter (#36922)

This creates a way for us to use boto3's data-driven waiter support to use custom waiters where Boto3 hasn't implemented them yet.

The only waiter implemented so far is for VPC Route Tables to check that they exist, and this replaces some custom retry code.
(cherry picked from commit a40bce2)

* Use NormalizedOperationMethod to catch ClientErrors so the waiter can handle them properly (#37356)

(cherry picked from commit c9e8aca)

* [cloud] Add custom waiters to stabilize ec2_vpc_subnet module - Fixes #36083 (#37534)

* stabilize ec2_vpc_subnet module

* Add waiters for ec2_vpc_subnet

Clean up integration tests

* Reenable CI for stabilized ec2_vpc_subnet tests

* rename waiters

* Use module_json_aws where applicable

Handle WaiterError first if waiting failed

* Fix traceback when tagging with keys/values that look like booleans

* Fix check mode with tags

* Add integration tests for tags that look like booleans and check mode

* Add waiter for deleting subnet

* Sleep a few seconds after using aws command line

(cherry picked from commit ea943e4)

* Fix sporadic errors in ec2_vpc_subnet integration tests (#38473)

(cherry picked from commit 46f13d3)

* [aws] Skip ec2_vpc_subnet waiters for old botocore versions (#39171)

 Fix ec2_vpc_subnet for botocore versions that do not accept the WaiterConfig parameter
(cherry picked from commit 6b91dae)

* [aws] Increase possible wait time for nonmonotonic subnet attributes (#38960)

(cherry picked from commit c4f0107)

* changelog
@ansible ansible locked and limited conversation to collaborators Apr 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue/PR relates to a bug. support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants