Closed JonTheNiceGuy closed 3 years ago
It looks like it's been resolved in the devel/2.x branch of the generator.
If you hit this issue, until a release with a fix is produced, the adjustment is to look for line ~249 in $YourCollectionsPath/ansible_collections/fortinet/fortios/plugins/modules/fortios_facts.py
, where it says fos = FortiOSHandler(connection)
and change it to fos = FortiOSHandler(connection, module)
thank you Jon for the detailed troubleshooting.
fortios_facts
is a legacy module, we team discussed about this module, we are going to fully deprecate this module in next major release as we are going to implement all monitor APIs which will cover the content of fortios_facts
.
we are going to build a hot collection to fix it in 1.1.x in days.
thanks again. Link
Given the following scenario:
When the following play is run:
The following result is seen (using -vvvvvv)
This is a regression between 1.0.11 and 1.1.4, and is because there's a difference between
module_utils/fortios/fortios.py
in each, that looks like this:This change was introduced here: https://github.com/fortinet-ansible-dev/fortios-ansible-generator/commit/0071ff75ad8c968a5bf2a4bbd8f30894d2f8ba48, but only appears to impact this one module (at least, without performing more robust testing!)