Error in repo

[micafili75project]

Hello everybody, we are trying to execute a playbook to configure some acl in fortigate. We have a fortigate virtual appliance with fortios 7.2.4. we have installed latest collection "ansible-galaxy collection install fortinet.fortios:2.3.4" and installed the required module... anyway during the exectuion of the playbook we had recived an error message: "error in repo" .. What's wrong...? I've tried to find the issue in previuos message in this forum, but I can't understand why it's still failing... can you help me ?

`---

• name: Configure Fortigate ACL hosts: fortigate01 gather_facts: no

  collections:

  • fortinet.fortios

  connection: httpapi vars: vdom: "root" ansible_httpapi_use_ssl: yes ansible_httpapi_validate_certs: no ansible_httpapi_port: 443 access_token: "xxxxxxxxxx"

  tasks:

  • name: Create ACL fortios_firewall_policy: access_token: "{{ access_token }}" state: "present" firewall_policy: policyid: 33 name: "test_ansible" srcintf:
    • name: "port1" dstintf:
    • name: "port2" srcaddr:
    • name: "all" dstaddr:
    • name: "all" action: "accept" schedule: "always" service:
    • name: "SSH"
    • name: "HTTP"
    • name: "HTTPS"
    • name: "WINRM" nat: "disable" comments: "Allow traffic to 172.20.108.22 for SSH, HTTP, HTTPS, and WinRM"

      policy_type: "policy"

      permit_any_host: "enable" `

[MaxxLiu22]

Hi @micafili75project ,

Thank you for raising this question, I run you script on my local, I find if I delete - name: "WINRM", everything works well, do you mean - name: "WINFRAME"?, since I don't find WINRM through CLI. Let me know if that doesn't fix your problem.

Thanks, Maxx

[micafili75project]

Hello Maxx, thank you for your replies... With WINRM i mean the winrm service on windows machine allows to connect to the remote powershell through this interface...Anyway removing the winrm section did the trick...!! Now the playbook does it work!! Thank you.. but let me say you,,, The error message mislead to a wrong conclusion... The error was not on repo either the module but in playbook itself... maybe somebody could try to change this beaviour