Closed Gittins closed 1 year ago
Files identified in the description: None
If these files are incorrect, please update the component name
section of the description or use the !component
bot command.
Thank you very much for your interest in Ansible. This plugin is not maintained in this repository and can be found at https://github.com/ansible-collections/ansible.netcommon
Please re-submit this issue in the above repository.
If you have further questions please stop by IRC or the mailing list:
Thanks for the response. I've logged the bug on the suggested git repo: https://github.com/ansible-collections/ansible.netcommon/issues/512
Summary
Using the ansible.netcommon.network_resource module against a working, from Ansible's point of view, network device (Cisco IOS, CSR1000V) fails when specific resource modules, that are known to be available for the device, are referenced.
The resource modules causing the failure have been identified as:
Issue Type
Bug Report
Component Name
ansible.netcommon.network_resource
Ansible Version
Configuration
OS / Environment
Targeted network device info:
The below table collates the device's hardware information:
The following table collates the device's software information:
Steps to Reproduce
Run the below playbook against the Cisco Always-On latest IOSXE device:
ciscoao_latest_iosxe: ansible_host: sandbox-iosxe-latest-1.cisco.com ansible_connection: ansible.netcommon.network_cli ansible_network_os: cisco.ios.ios ansible_user: developer ansible_password: C1sco12345
Expected Results
The first task in the playbook registers all the available modules for the device/host being targeted, with the subsequent task outputting them so we can see what's available.
The "Fetch config for working modules" task contains a partial list of the modules found to be available, which it runs through, as expected. The first 2 modules in the list work without issue and their outputs are collected. The last module "vlans" fails with an appropriate error message, which I have no real issue with (there are no vlans on the device, so this could be the cause).
However, the "Fetch config for failing modules" task contains the list of modules I've isolated down which cause the task to fail with a python based error, when targeting either 1 or all of them. This is the issue that is completely breaking things for me and I'd like help understanding and, if possible, fixing.
Actual Results
Code of Conduct