Cannot remove A records via dnsmadeeasy #38730
Comments
<!--- Your description here --> If you omit the record type on state absent you will get "record_type not yet supported". Although in my experience so far, if you put the record type it still fails to remove the record but it doesn't crash. (ansible#38730) +label: docsite_pr
|
Files identified in the description: If these files are inaccurate, please update the |
ansibot
added
affects_2.5
mkrizek
removed
the
needs_triage
<!--- Your description here --> If you omit the record type on state absent you will get "record_type not yet supported". Although in my experience so far, if you put the record type it still fails to remove the record but it doesn't crash. (ansible#38730) +label: docsite_pr
<!--- Your description here --> If you omit the record type on state absent you will get "record_type not yet supported". Although in my experience so far, if you put the record type it still fails to remove the record but it doesn't crash. (ansible#38730) +label: docsite_pr
<!--- Your description here --> If you omit the record type on state absent you will get "record_type not yet supported". Although in my experience so far, if you put the record type it still fails to remove the record but it doesn't crash. (ansible#38730) +label: docsite_pr
|
This bug also applies to record_type |
|
I was able to delete the record successfully if I include the proper value for it looks like if no |
|
@NickLavrov Thanks! That sort of makes sense. They event comment just above that there can be |
|
@BlackthornYugen The documentation is incorrect or misleading, unfortunately: seems to imply that you don't need fwiw, I ended up adding some logic that uses |
|
@NickLavrov thanks! I did the same thing now. Updated my code to query records and remove them explicitly. |
ansibot
added
support:core
|
I don't think it is a proper logic. I believe the old behavior was the correct one. It now creates a round robin if I simply say present with the same name. That forces me to delete before add to update and then I have to also now make sure I am querying some values and making sure I compare them to new ones. Why not the author just have a flag allowing to remove all records based just on name and another flag to update based on the record name (update if the same name, or add new if no record name exist). |
ansibot
added
needs_maintainer
<!--- Your description here --> If you omit the record type on state absent you will get "record_type not yet supported". Although in my experience so far, if you put the record type it still fails to remove the record but it doesn't crash. (ansible#38730) +label: docsite_pr
ansibot
removed
the
needs_maintainer
ansibot
added
collection
|
Thank you very much for your interest in Ansible. Ansible has migrated much of the content into separate repositories to allow for more rapid, independent development. We are closing this issue/PR because this content has been moved to one or more collection repositories.
For further information, please see: |
ISSUE TYPE
COMPONENT NAME
dnsmadeeasy
ANSIBLE VERSION
CONFIGURATION
ANSIBLE_COW_SELECTION(env: ANSIBLE_COW_SELECTION) = random
DISPLAY_ARGS_TO_STDOUT(env: ANSIBLE_DISPLAY_ARGS_TO_STDOUT) = True
OS / ENVIRONMENT
OSX targeting CENTOS 7
SUMMARY
When removing an A record using DNS Made Easy's module, the module says nothing happened. That's correct, it will never remove a DNS A record. The documentation says you don't need to specify the record type when removing, but it will throw an exception if you omit this. When you include the type "A" record it does nothing ever.
STEPS TO REPRODUCE
EXPECTED RESULTS
Previous DNS A Record would be deleted and new record would be added
ACTUAL RESULTS
The previous DNS A Record remains in addition to the new record.
{ "changed": false, "invocation": { "module_args": { "account_key": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER", "account_secret": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER", "autoFailover": false, "contactList": null, "domain": "trst.ca", "failover": false, "httpFile": null, "httpFqdn": null, "httpQueryString": null, "ip1": null, "ip2": null, "ip3": null, "ip4": null, "ip5": null, "maxEmails": 1, "monitor": false, "port": 80, "protocol": "HTTP", "record_name": "ansible", "record_ttl": 1800, "record_type": "A", "record_value": null, "sensitivity": "Medium", "state": "absent", "systemDescription": "", "validate_certs": true } } }Before execution
After execution
The text was updated successfully, but these errors were encountered: