You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Traceback (most recent call last):
File "<stdin>", line 107, in <module>
File "<stdin>", line 99, in _ansiballz_main
File "<stdin>", line 47, in invoke_module
File "/usr/lib/python3.8/runpy.py", line 207, in run_module
return _run_module_code(code, init_globals, run_name, mod_spec)
File "/usr/lib/python3.8/runpy.py", line 97, in _run_module_code
_run_code(code, mod_globals, init_globals,
File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/tmp/ansible_fortinet.fortios.fortios_firewall_policy_payload_q02j_ql7/ansible_fortinet.fortios.fortios_firewall_policy_payload.zip/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy.py", line 11647, in <module>
File "/tmp/ansible_fortinet.fortios.fortios_firewall_policy_payload_q02j_ql7/ansible_fortinet.fortios.fortios_firewall_policy_payload.zip/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy.py", line 11613, in main
ValueError: too many values to unpack (expected 4)
and (resp["revision_changed"] if"revision_changed"inrespelseTrue),
resp,
{},
)
Furthermore, looking at the code, I doubt that check mode is even honored (since the check_mode parameter isn't even passed to to move_fortios_firewall()) and the move is carried out anyway (but I didn't verify).
The text was updated successfully, but these errors were encountered:
Thank you for raising this issue, I can reproduce that, there do are some problems around check operation, I have reported it along with your previous issue to the development team.
Invocation:
Leads to this error in check mode (
-C
):My guess is that this code segment is to blame:
ansible-galaxy-fortios-collection/plugins/modules/fortios_firewall_policy.py
Lines 2111 to 2128 in 289ee01
Furthermore, looking at the code, I doubt that check mode is even honored (since the
check_mode
parameter isn't even passed to tomove_fortios_firewall()
) and the move is carried out anyway (but I didn't verify).The text was updated successfully, but these errors were encountered: