-
Notifications
You must be signed in to change notification settings - Fork 48
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
fortios_system_dns #47
Comments
Hi @RichardBotham, Can you please check the runtime module is the one in galaxy collection not the old ansible module? I've noticed hosts, username, password, ssl_verify, https parameters used in the playbook, they'are actually causing the issue you mentioned above. We use ansible_httpapi_use_ssl [yes/no] and ansible_httpapi_validate_certs [yes/no] instead in collection. And please note if you're using hosts, username, password in the playbook, then the old ansible modules will be called not the ones in collection. FYI, here's a workable playbook.
You can config the hosts file under /etc/ansible/hosts and no need to use them in the playbook. [fortigateslab] [fortigateslab:vars] |
@RichardBotham hi Rich,
but first make it clear which fortios version it is and install correct fortios collection. I mark this thanks, |
Issue with the domain keyword in fortios_system_dns module when using fortinet.fortios collection
ansible version 2.9.7
fortios 6.0.9
When running this playbook an error is generated as follows
Error
When the playbook is amended as follows the module operates as expected
This is the output
This is the resulting configuration
The text was updated successfully, but these errors were encountered: