Noriko Hosoi 023ecbd027 Collections - workaround for the module_utils path finding issue in ansible 2.9 ... The details of the issue is described in this ansible issue: https://github.com/ansible/ansible/issues/68361 The workaround contains 2 changes. 1) Advice from @sivel: replacing, e.g., from ansible.module_utils.network_lsr.nm.provider import NetworkManagerProvider with from ansible.module_utils.network_lsr.nm import provider and then use provider.NetworkManagerProvider 2) In the later module_utils path finding path, gi.require_version("NM", "1.0") in module_utils/network_lsr/nm/client.py fails with "ValueError: Namespace NM not available" on the control node. By ignoring the exception, the failure is worked around. Please note that the missing package issue never occurs on the managed nodes since in case of "nm", the NetworkManager package is installed in the network role. Signed-off-by: Noriko Hosoi <nhosoi@redhat.com>		2021-01-14 17:04:10 -05:00
..
network_lsr	Collections - workaround for the module_utils path finding issue in ansible 2.9	2021-01-14 17:04:10 -05:00
__init__.py	Add Pytest integration tests	2020-08-24 21:52:25 +02:00