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
{
"exception": "Traceback (most recent call last):\n File \"<stdin>\", line 102, in <module>\n File \"<stdin>\", line 94, in _ansiballz_main\n File \"<stdin>\", line 40, in invoke_module\n File \"/usr/lib64/python2.7/runpy.py\", line 170, in run_module\n mod_name, loader, code, fname = _get_module_details(mod_name)\n File \"/usr/lib64/python2.7/runpy.py\", line 103, in _get_module_details\n raise ImportError(\"No module named %s\" % mod_name)\nImportError: No module named ansible.modules.ios_command\n",
"_ansible_no_log": false,
"module_stderr": "Traceback (most recent call last):\n File \"<stdin>\", line 102, in <module>\n File \"<stdin>\", line 94, in _ansiballz_main\n File \"<stdin>\", line 40, in invoke_module\n File \"/usr/lib64/python2.7/runpy.py\", line 170, in run_module\n mod_name, loader, code, fname = _get_module_details(mod_name)\n File \"/usr/lib64/python2.7/runpy.py\", line 103, in _get_module_details\n raise ImportError(\"No module named %s\" % mod_name)\nImportError: No module named ansible.modules.ios_command\n",
"changed": false,
"module_stdout": "",
"rc": 1,
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error"
}
So far everything works on Ansible 2.8.6, but this seems to break on Ansible 2.9. Has it something to do with collections? I can use the ios_command module fine when not using this provider role. I will be downloading this and making some modifications in order for it to work on 2.9.
The text was updated successfully, but these errors were encountered:
So far everything works on Ansible 2.8.6, but this seems to break on Ansible 2.9. Has it something to do with collections? I can use the ios_command module fine when not using this provider role. I will be downloading this and making some modifications in order for it to work on 2.9.
The text was updated successfully, but these errors were encountered: