You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updating the Listener Rules of an existing elbv2 load balancer via elb_application_lb successfully modifies the rules but raises an exception while parsing the response. If no update is made (e.g. playbook is run again after the failed run) then it correctly returns [OK].
ISSUE TYPE
Bug Report
COMPONENT NAME
elb_application_lb
STEPS TO REPRODUCE
Run playbook with some ELB rules, creating the ELB for the first time - Observe success
Modify parameters of one of the rules slightly, re-run playbook - Observe failure, but note that rules have updated in AWS console.
Re-run playbook again - Observe [OK].
The particular playbook I see this on has one source-ip rule, 5-13 host-header rules with forward actions, and a fixed-response default action. I'm not sure if it's specifically any of those which are causing the issue or if it happens more generally.
ACTUAL RESULTS
[WARNING]: Module invocation had junk after the JSON data:
... (massive blob of JSON representing the elb configuration)
fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "", "module_stdout": "modified_rule:" ... (massive blob of JSON representing the elb configuration) ... \\n", "msg": "MODULE FAILURE\\nSee stdout/stderr for the exact error", "rc": 0}
The text was updated successfully, but these errors were encountered:
SUMMARY
Updating the Listener Rules of an existing elbv2 load balancer via elb_application_lb successfully modifies the rules but raises an exception while parsing the response. If no update is made (e.g. playbook is run again after the failed run) then it correctly returns [OK].
ISSUE TYPE
COMPONENT NAME
elb_application_lb
STEPS TO REPRODUCE
Run playbook with some ELB rules, creating the ELB for the first time - Observe success
Modify parameters of one of the rules slightly, re-run playbook - Observe failure, but note that rules have updated in AWS console.
Re-run playbook again - Observe [OK].
The particular playbook I see this on has one
source-ip
rule, 5-13host-header
rules withforward
actions, and afixed-response
default action. I'm not sure if it's specifically any of those which are causing the issue or if it happens more generally.ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: