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

AWS elb_target_group requires protocol, port when state is absent #68760

Closed
TC-robV opened this issue Apr 7, 2020 · 3 comments
Closed

AWS elb_target_group requires protocol, port when state is absent #68760

TC-robV opened this issue Apr 7, 2020 · 3 comments
Labels
affects_2.9 This issue/PR affects Ansible v2.9 aws bug This issue/PR relates to a bug. cloud module This issue/PR relates to a module. python3 support:community This issue/PR relates to code supported by the Ansible community.

Comments

@TC-robV
Copy link

TC-robV commented Apr 7, 2020

SUMMARY

when trying to delete a target group via elb_target_group it throws
target_type is instance but all of the following are missing: protocol, port.
double checked and eve in the docs it says those are only needed if state is present

ISSUE TYPE
  • Bug Report
COMPONENT NAME

elb_target_group

ANSIBLE VERSION
ansible 2.9.6
  config file = /Users/xx/.ansible.cfg
  configured module search path = ['/Users/xx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/xx/python-env/ansible2.9/lib/python3.7/site-packages/ansible
  executable location = /Users/xx/python-env/ansible2.9/bin/ansible
  python version = 3.7.7 (default, Mar 10 2020, 15:43:33) [Clang 11.0.0 (clang-1100.0.33.17)]

OS / ENVIRONMENT

macos 10.15.4

STEPS TO REPRODUCE
- name: Delete Target Groups
  elb_target_group:
    region: "{{ tt_region }}"
    profile: "{{ profile }}"
    name: "{{ tt_env_short }}-{{ item.name }}"
    vpc_id: "{{ vpc.vpcs[0].id }}"
    state: absent

EXPECTED RESULTS

delete with no error.

ACTUAL RESULTS

it throws an error about needed the protocol and port during state=absent.
if i put in random protocol and port it works fine.

@ansibot
Copy link
Contributor

ansibot commented Apr 7, 2020

Files identified in the description:

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

@ansibot
Copy link
Contributor

ansibot commented Apr 7, 2020

@TC-robV, just so you are aware we have a dedicated Working Group for aws.
You can find other people interested in this in #ansible-aws on Freenode IRC
For more information about communities, meetings and agendas see https://github.com/ansible/community

click here for bot help

@ansibot ansibot added affects_2.9 This issue/PR affects Ansible v2.9 aws bug This issue/PR relates to a bug. cloud module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. python3 support:community This issue/PR relates to code supported by the Ansible community. labels Apr 7, 2020
@sivel
Copy link
Member

sivel commented Apr 13, 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:

@sivel sivel closed this as completed Apr 13, 2020
@sivel sivel removed the needs_triage Needs a first human triage before being processed. label Apr 14, 2020
@ansible ansible locked and limited conversation to collaborators May 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.9 This issue/PR affects Ansible v2.9 aws bug This issue/PR relates to a bug. cloud module This issue/PR relates to a module. python3 support:community This issue/PR relates to code supported by the Ansible community.
Projects
None yet
Development

No branches or pull requests

3 participants