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

route53_health_check resource_path uniqueness ignored #23110

Closed
jameelur opened this issue Mar 30, 2017 · 6 comments
Closed

route53_health_check resource_path uniqueness ignored #23110

jameelur opened this issue Mar 30, 2017 · 6 comments
Labels
affects_2.2 This issue/PR affects Ansible v2.2 aws bug This issue/PR relates to a bug. cloud collection:community.aws collection Related to Ansible Collections work module This issue/PR relates to a module. needs_collection_redirect https://github.com/ansible/ansibullbot/blob/master/docs/collection_migration.md support:community This issue/PR relates to code supported by the Ansible community.

Comments

@jameelur
Copy link

ISSUE TYPE
  • Bug Report
COMPONENT NAME

route53_health_check

ANSIBLE VERSION
ansible 2.2.2.0
CONFIGURATION

N/A

OS / ENVIRONMENT

Mac OSX

SUMMARY

Tried to create multiple route53 healthchecks to the same server but different resource paths using with_items . Instead of creating one health check for each resource path, only the first is created.

STEPS TO REPRODUCE
- name: set up route53 health checks
  connection: local
  become: false
  route53_health_check:
    failure_threshold: 3
    ip_address: '{{ ip_address }}'
    port: 80
    request_interval: 30
    resource_path: '{{ item }}'
    state: present
    type: HTTP
  register: result
  with_items:
    - /some_status1
    - /other_status2
EXPECTED RESULTS
  • 2 health checks created
  • result contains health_check.ids for each health check
ACTUAL RESULTS
  • 1 health check created
  • result contains two items, both having the same health_check.id
@jameelur
Copy link
Author

Possibly related to ansible/ansible-modules-core#2847
After that report was closed, I could find no equivalent on either core nor extra repos

@ansibot
Copy link
Contributor

ansibot commented Mar 30, 2017

@ansibot ansibot added affects_2.2 This issue/PR affects Ansible v2.2 aws bug_report cloud module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. labels Mar 30, 2017
@Qalthos Qalthos removed the needs_triage Needs a first human triage before being processed. label Mar 30, 2017
@ansibot ansibot added the support:community This issue/PR relates to code supported by the Ansible community. label Jun 29, 2017
@ansibot
Copy link
Contributor

ansibot commented Jul 18, 2017

@ansibot ansibot added bug This issue/PR relates to a bug. and removed bug_report labels Mar 1, 2018
@ansibot
Copy link
Contributor

ansibot commented Feb 1, 2020

@ansibot ansibot added collection Related to Ansible Collections work collection:community.aws needs_collection_redirect https://github.com/ansible/ansibullbot/blob/master/docs/collection_migration.md labels Apr 29, 2020
@sydoluciani
Copy link

@jameel263 route53 modules along other community supported aws modules have been moved to
community.aws

I have created a new issue in community.aws repository

Please close this issue.

Thank you

@mkrizek
Copy link
Contributor

mkrizek commented Jun 6, 2020

Thanks @sydoluciani!

@mkrizek mkrizek closed this as completed Jun 6, 2020
@ansible ansible locked and limited conversation to collaborators Jul 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.2 This issue/PR affects Ansible v2.2 aws bug This issue/PR relates to a bug. cloud collection:community.aws collection Related to Ansible Collections work module This issue/PR relates to a module. needs_collection_redirect https://github.com/ansible/ansibullbot/blob/master/docs/collection_migration.md support:community This issue/PR relates to code supported by the Ansible community.
Projects
None yet
Development

No branches or pull requests

5 participants