search

fortinet-ansible-dev / ansible-galaxy-fortios-collection

GNU General Public License v3.0
85 stars 49 forks source link

ConnectionError: command timeout triggered #333

Closed Tiguespa closed 3 months ago

Tiguespa commented 3 months ago

Hello guys, it's me again with another issue i can't figure. I have a vm in 7.0.15 and a physical in 7.0.15 (FG120G)

ansible [core 2.15.12] tested with fortios 2.3.6 and 2.3.7

Tried my playbooks after few days (was working fine for all), and today it's broken on the physical Indeed, the playbooks works perfectly fine on my VM but not on my physical. Exported the vm config into the physical to see if it was something i changed (spoiler, didn't change anything) Tried everything i could think of and it's always fine on my VM but always the same error on physical

ansible.module_utils.connection.ConnectionError: command timeout triggered, timeout value is 30 secs. See the timeout setting options in the Network Debug and Troubleshooting Guide.

The Log event on physical see my connections " Message Administrator admin logged in successfully from https ".

I'm pretty convinced it's a me problem , but i can't see what i'm missing on this one.

Playbook : 

---
- name: Get FORTI conf
  hosts:
    - FORTIA
  gather_facts: no
  ignore_errors: yes
  tasks:

    - name: Will generate the playbooks for each selector/module.
      fortinet.fortios.fortios_export_config_playbook:
          selectors:
              - selector: system_interface

          output_path: "./{{ ansible_name }}/"

Error : 

ansible.module_utils.connection.ConnectionError: command timeout triggered, timeout value is 30 secs.
See the timeout setting options in the Network Debug and Troubleshooting Guide.
fatal: [LAB1_FORTI1_A]: FAILED! => {
    "changed": false,
    "module_stderr": "Traceback (most recent call last):\n  File \"/home/okok/.ansible/tmp/ansible-local-240750824mazy6/ansible-tmp-1721380793.616424-240754-116248594734932/AnsiballZ_fortios_export_config_playbook.py\", line 107, in <module>\n    _ansiballz_main()\n  File \"/home/okok/.ansible/tmp/ansible-local-240750824mazy6/ansible-tmp-1721380793.616424-240754-116248594734932/AnsiballZ_fortios_export_config_playbook.py\", line 99, in _ansiballz_main\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n  File \"/home/okok/.ansible/tmp/ansible-local-240750824mazy6/ansible-tmp-1721380793.616424-240754-116248594734932/AnsiballZ_fortios_export_config_playbook.py\", line 47, in invoke_module\n    runpy.run_module(mod_name='ansible_collections.fortinet.fortios.plugins.modules.fortios_export_config_playbook', init_globals=dict(_module_fqn='ansible_collections.fortinet.fortios.plugins.modules.fortios_export_config_playbook', _modlib_path=modlib_path),\n  File \"<frozen runpy>\", line 226, in run_module\n  File \"<frozen runpy>\", line 98, in _run_module_code\n  File \"<frozen runpy>\", line 88, in _run_code\n  File \"/tmp/ansible_fortinet.fortios.fortios_export_config_playbook_payload_a44j5f6j/ansible_fortinet.fortios.fortios_export_config_playbook_payload.zip/ansible_collections/fortinet/fortios/plugins/modules/fortios_export_config_playbook.py\", line 6842, in <module>\n  File \"/tmp/ansible_fortinet.fortios.fortios_export_config_playbook_payload_a44j5f6j/ansible_fortinet.fortios.fortios_export_config_playbook_payload.zip/ansible_collections/fortinet/fortios/plugins/modules/fortios_export_config_playbook.py\", line 6805, in main\n  File \"/tmp/ansible_fortinet.fortios.fortios_export_config_playbook_payload_a44j5f6j/ansible_fortinet.fortios.fortios_export_config_playbook_payload.zip/ansible_collections/fortinet/fortios/plugins/modules/fortios_export_config_playbook.py\", line 5214, in fortios_configuration_fact\n  File \"/tmp/ansible_fortinet.fortios.fortios_export_config_playbook_payload_a44j5f6j/ansible_fortinet.fortios.fortios_export_config_playbook_payload.zip/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/fortios.py\", line 595, in get\n  File \"/tmp/ansible_fortinet.fortios.fortios_export_config_playbook_payload_a44j5f6j/ansible_fortinet.fortios.fortios_export_config_playbook_payload.zip/ansible/module_utils/connection.py\", line 200, in __rpc__\nansible.module_utils.connection.ConnectionError: command timeout triggered, timeout value is 30 secs.\nSee the timeout setting options in the Network Debug and Troubleshooting Guide.\n"

Thanks

Tiguespa commented 3 months ago

Well sorry , i found the issue. Nothing to do with forti, it seems my router would drop any command result from my playbook if it wasn't on the exact same network.