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.

Sign up for GitHub

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

Jump to bottom

Cloudflare DNS does not allow for tls protocol type #36708

Closed
DennisGlindhart opened this issue Feb 26, 2018 · 3 comments · Fixed by #36709
Closed

Cloudflare DNS does not allow for tls protocol type #36708

DennisGlindhart opened this issue Feb 26, 2018 · 3 comments · Fixed by #36709
Labels
affects_2.4 This issue/PR affects Ansible v2.4 bug This issue/PR relates to a bug. has_pr This issue has an associated PR. module This issue/PR relates to a module. net_tools Net-tools category support:community This issue/PR relates to code supported by the Ansible community.

Comments

@DennisGlindhart
Copy link
Contributor

ISSUE TYPE
  • Bug Report
COMPONENT NAME

cloudflare_dns

ANSIBLE VERSION
ansible 2.4.3.0
  python version = 2.7.14 (default, Feb 17 2018, 10:42:17) [GCC 7.3.1 20180130 (Red Hat 7.3.1-2)]
CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

Cloudflare DNS module does not allow for SRV-records of type tls - only tcp and udp are allowed. Cloudflare also supports tls-type.

STEPS TO REPRODUCE
- cloudflare_dns:
    domain: my.com
    service: foo
    proto: tls
    port: 3500
    priority: 10
    weight: 20
    type: SRV
    value: fooserver.my.com
EXPECTED RESULTS

Not failing

ACTUAL RESULTS
TASK [dns : cloudflare_dns] ***********************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "value of proto must be one of: tcp,udp, got: tls"}
@ansibot
Copy link
Contributor

ansibot commented Feb 26, 2018

Files identified in the description:

If these files are inaccurate, 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 Feb 26, 2018

cc @andreaso @mgruener
click here for bot help

@ansibot ansibot added affects_2.4 This issue/PR affects Ansible v2.4 bug_report module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. net_tools Net-tools category support:community This issue/PR relates to code supported by the Ansible community. labels Feb 26, 2018
@DennisGlindhart DennisGlindhart mentioned this issue Feb 26, 2018
Merged
@Akasurde
Copy link
Member

resolved_by_pr #36709

@Akasurde Akasurde added has_pr This issue has an associated PR. and removed needs_triage Needs a first human triage before being processed. labels Feb 26, 2018
@ansibot ansibot added bug This issue/PR relates to a bug. and removed bug_report labels Mar 1, 2018
@ansible ansible locked and limited conversation to collaborators Apr 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
affects_2.4 This issue/PR affects Ansible v2.4 bug This issue/PR relates to a bug. has_pr This issue has an associated PR. module This issue/PR relates to a module. net_tools Net-tools category support:community This issue/PR relates to code supported by the Ansible community.
Projects
None yet
Milestone
No milestone
3 participants
@Akasurde @DennisGlindhart @ansibot