elb_application_lb Updating Listener Rules Of Existing LB Fails After Edit

[Alex-Richman]

Copied from ansible/ansible#69017

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

• 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

elb_application_lb:
  state: present
  ...
  listeners:
    ...
    Rules:
      ...
      - Type: fixed-response
         FixedResponseConfig:
         StatusCode: "403"
         ContentType: "text/plain"
         MessageBody: Forbidden

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}

[briantist]

I'm not certain but it might be related to this issue:
https://github.com/ansible-collections/amazon.aws/issues/8

Which is in the other collection because most of the code for the elbv2 modules is in the module util, which is in the other collection, while the modules are here in this one 😕

[ansibullbot]

@Alex-Richman: Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information.

Here are the items we could not find in your description:

• ansible version

Please set the description of this issue with this template:
https://raw.githubusercontent.com/ansible/ansible/devel/.github/ISSUE_TEMPLATE/bug_report.md

click here for bot help

[ansibullbot]

cc @jillr @s-hertel @tremble @wimnat
click here for bot help

[gravesm]

@Alex-Richman Thank you for reporting this! This has been fixed in module_utils but not yet released. Could you try the latest main branch of amazon.aws and see if this fixes your problem?

[jatorcasso]

@markuman can we mark this as closed?

[markuman]

Yes. Thanks for investigate here @jatorcasso