Closed janorga closed 3 months ago
Build succeeded. https://ansible.softwarefactory-project.io/zuul/buildset/153d2c4aae784505a6756137041df0cd
:heavy_check_mark: ansible-galaxy-importer SUCCESS in 4m 03s :heavy_check_mark: build-ansible-collection SUCCESS in 6m 44s
Build succeeded. https://ansible.softwarefactory-project.io/zuul/buildset/1ccd85a300624a628bc24f6b2730800e
:heavy_check_mark: ansible-galaxy-importer SUCCESS in 4m 20s :heavy_check_mark: build-ansible-collection SUCCESS in 7m 02s
changelog fragment is added
Build succeeded. https://ansible.softwarefactory-project.io/zuul/buildset/599fddc0f0734620a8a59b456bed4f31
:heavy_check_mark: ansible-galaxy-importer SUCCESS in 2m 56s :heavy_check_mark: build-ansible-collection SUCCESS in 6m 54s
thank you @janorga for this meaningful contribution :clap:
Thank you too for all your effort guys!
SUMMARY
the module ansible.utils.cli_parse fails on network device with error "/bin/sh: 1: show: not found\n".
Fix to Issue: ID 347
ISSUE TYPE
Bug Fix
COMPONENT NAME
cli_parse
Aditional information
It seems that an update has been introduced at ansible.utils release v3.1.0 which prevents Ansible to correctly connecting to the network asset using the instructed connection. Tests done previous to this fix are performed against a Cisco NXOS host. Ansible could not connect to the network asset using the instructed
ansible.netcommon.network_cli
.Check #347 for details.