-
Notifications
You must be signed in to change notification settings - Fork 342
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
Exception modifying rule with existing HttpRequestMethodConfig #187
Comments
Additional Issue SummaryI looked into this issue some more and have found that it actually impacts multiple rule configurations, including http-header, http-request-method, host-header, path-pattern, and query-string. I noticed that there was already a special condition for when 'SourceIpConfig' is present, so source-ip is not impacted. Note that host-header and path-pattern fields can be defined using Values directly, without HostHeaderConfig or PathPatternConfig. This may be why the issue has not already been addressed. When using HostHeaderConfig/PathPatternConfig though, they have the same issue. Related MaterialSimilar issue with http-header config. Expanded Steps to ReproduceSee sample playbook at https://gist.github.com/bradleypettit/351d5a1c576eba826bbafd2f016550c9. There is a task for each Rule field mentioned above. Each task runs twice, the first successfully creates the ALB, and the second execution fails with KeyError. |
Closing as this is duplicate of ansible-collections/community.aws#117. |
Thank you for reporting the issue @bradleypettit |
This should initially fail and be fixed the day ansible-collections/amazon.aws#188 is merged. See: ansible-collections/amazon.aws#187 See: ansible-collections#117
This should initially fail and be fixed the day ansible-collections/amazon.aws#188 is merged. See: ansible-collections/amazon.aws#187 See: ansible-collections#117
This should initially fail and be fixed the day ansible-collections/amazon.aws#188 is merged. See: ansible-collections/amazon.aws#187 See: ansible-collections#117
* elb_application_lb: test a rule based on http-header This should initially fail and be fixed the day ansible-collections/amazon.aws#188 is merged. See: ansible-collections/amazon.aws#187 See: #117 Co-authored-by: Mark Chappell <[email protected]>
…ble-collections#187) * Split imports into a single line * Increase the max_attempts retries for the ec2_instance tests, we're running a *lot* in parallel which triggers RateLimiting errors
…ble-collections#187) * Split imports into a single line * Increase the max_attempts retries for the ec2_instance tests, we're running a *lot* in parallel which triggers RateLimiting errors
…ble-collections#187) * Split imports into a single line * Increase the max_attempts retries for the ec2_instance tests, we're running a *lot* in parallel which triggers RateLimiting errors
…ble-collections#187) * Split imports into a single line * Increase the max_attempts retries for the ec2_instance tests, we're running a *lot* in parallel which triggers RateLimiting errors
…ions#347) * elb_application_lb: test a rule based on http-header This should initially fail and be fixed the day ansible-collections/amazon.aws#188 is merged. See: ansible-collections/amazon.aws#187 See: ansible-collections#117 Co-authored-by: Mark Chappell <[email protected]>
…ions#347) * elb_application_lb: test a rule based on http-header This should initially fail and be fixed the day ansible-collections/amazon.aws#188 is merged. See: ansible-collections/amazon.aws#187 See: ansible-collections#117 Co-authored-by: Mark Chappell <[email protected]>
…ions#347) * elb_application_lb: test a rule based on http-header This should initially fail and be fixed the day ansible-collections/amazon.aws#188 is merged. See: ansible-collections/amazon.aws#187 See: ansible-collections#117 Co-authored-by: Mark Chappell <[email protected]>
…ions#347) * elb_application_lb: test a rule based on http-header This should initially fail and be fixed the day ansible-collections/amazon.aws#188 is merged. See: ansible-collections/amazon.aws#187 See: ansible-collections#117 Co-authored-by: Mark Chappell <[email protected]>
* elb_application_lb: test a rule based on http-header This should initially fail and be fixed the day #188 is merged. See: #187 See: ansible-collections/community.aws#117 Co-authored-by: Mark Chappell <[email protected]> This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@8c0ea48
…ions#347) * elb_application_lb: test a rule based on http-header This should initially fail and be fixed the day ansible-collections#188 is merged. See: ansible-collections#187 See: ansible-collections/community.aws#117 Co-authored-by: Mark Chappell <[email protected]> This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@8c0ea48
…ble-collections#187) * Split imports into a single line * Increase the max_attempts retries for the ec2_instance tests, we're running a *lot* in parallel which triggers RateLimiting errors
…ble-collections#187) * Split imports into a single line * Increase the max_attempts retries for the ec2_instance tests, we're running a *lot* in parallel which triggers RateLimiting errors
…ble-collections#187) * Split imports into a single line * Increase the max_attempts retries for the ec2_instance tests, we're running a *lot* in parallel which triggers RateLimiting errors
SUMMARY
Using community.aws.elb_application_lb we have found that you are not able to modify existing routing rules if the condition field is 'http-request-method'. It is possible to create/update an ALB and add a rule using http-request-method in the first instance. However any subsequent executions of the same task, or trying to modify the routing rule, result in a KeyError exception. As shown below, community.aws.elb_application_lb is relying on the elbv2 module_util to compare the rule conditions.
ISSUE TYPE
COMPONENT NAME
elbv2.py
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
It's expected that the above task would in the first instance create a new load balancer, and on subsequent runs execute successfully with no changes.
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: