Closed faizan-syed closed 1 year ago
Hi @faizan-syed ,
Thank you for raising this issue, your script works well on my side, may I know which fortinet.fortios collection are you using? type ansible-galaxy collection list
to get these information, I use
ansible.netcommon 5.1.1
ansible.utils 2.10.3
fortinet.fortios 2.3.0
ipv4trusthost changed to ipv4-trusthost is expected, in ansible we use "" but in API we use "-", there is a conversion to satisfy two platform's coding standard.
Thanks, Maxx
Hi @MaxxLiu22 ,
I am using the below collection:-
"fortinet.fortios": "==2.1.6" "ansible.netcommon": "==3.0.1" "ansible.utils": "==2.8.0"
I am running the ansible roles from jenkins pipeline to configure the fortigate.If you see the above error output its showing as Trusthost IP address can not be empty in cli error , even I have defined the ipv4_trusthost and showing msg": "Error in repo" . I am unable to figure out why its coming like that , any suggestion would be really helpful
The issue is resolved after I upgrade the fortinet.fortios to 2.3.0
Hi , My ansible playbook is failing when I am trying to create API admin user from the api profile while giving trusthost IP address. It worked fine without ipv4_trusthost but when I defined it as below it failed
It failed with below error
@FTNT-HQCM @MaxxLiu22 https://docs.ansible.com/ansible/latest/collections/fortinet/fortios/fortios_system_api_user_module.html
Need help in this ? why in the output ipv4_trusthost changed to ipv4-trusthost automatically ???