10-14-2019 11:58 PM
I'm from the Red Hat's Ansible support team. I've opened this request as part of partner engagement with Infoblox on behalf of a customer. We have two cases with us by a customer. The customer is having issues with the Infoblox Ansible module nios_txt_record
`Ansible nios_txt_record module replaces existing TXT records instead of adding additional records.`
Details about the issues can be found in the below link opened in our Ansible Github repository https://github.com/ansible/ansible/issues/62377 .
We had pinged Sailesh Giri and Kris Vasudevan on our Ansible Github issue link https://github.com/ansible/ansible/issues/62377 to get someone to work on the Infoblox module but haven't got a reply. I've gone through a support case with Infoblox but they have redirected me here. The Infoblox modules are certified and provided by Infoblox as part of our partner program. We are requesting a collaboration on the issue mentioned above to get a fix out for the module. Ansible will do the needful to include in the applicable releases once a suitable fix is provided.
Senior Technical Support Engineer,
10-16-2019 12:06 AM
it looks like this depends on github.com/infobloxopen/infoblox-client
This module does not support txt records, I have just made a pull request to include them. Once that gets merged the behavior should be in line with expectations.
10-16-2019 01:36 PM
You are wrong. The nios_txt_record module was introduced in Ansible 2.7:
The problem is the TXT module was never tested before it was released into production. Infoblox releases alpha quality code to the community and then takes months to fix problems after they are reported.
I reported back in January that you couldn't add the same record to two different views using nios_a_record, even though it specifically supported views. That didn't get fixed until mid-March.
Turns out the same problem exists with the nios_ptr_record module too:
The problem with nio_ptr_record was reported in June and it's still not fixed! Based on past history, I can expect a fix for nios_txt_record sometime next spring.
Infoblox signed on to the Red Hat Red Hat Ansible Automation Certification Program and promised to "provide tested, trusted and supported solutions for automating across environments at scale"
As a paying Infoblox customer who has worked with your Ansible NIOS modules, I can attest to the fact that Infoblox's Ansible modules are NOT TESTED, CANNOT BE TRUSTED AND ARE NOT SUPPORTED.
a month ago - last edited a month ago
The customer (WRJFontenot) is still waiting.
Technical Support Engineer, Ansible
2 weeks ago
I took a look at the comment line of the issue, but there seems to be no update in a month.
Is anyone working on this issue? We would like to know the status of this issue.
Senior Software Maintenance Engineer
2 weeks ago
We are actively looking into resolving this issue. I'll keep you posted.
Thanks and regards,