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

elb_application_lb Updating Listener Rules Of Existing LB Fails After Edit #69017

Closed
Alex-Richman opened this issue Apr 18, 2020 · 1 comment
Closed

Comments

@Alex-Richman
Copy link
Contributor

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}
@sivel
Copy link
Member

sivel commented Apr 20, 2020

Thank you very much for your interest in Ansible. This plugin is no longer maintained in this repository and has been migrated to https://github.com/ansible-collections/community.aws

Please re-submit this issue in the above repository.

If you have further questions please stop by IRC or the mailing list:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants