Closed NoxInmortus closed 4 years ago
It could be that this was fixed in #120 by @ganeshrn. The fix will be included in the next community.network release (scheduled for end of November).
Hello @felixfontein is there a way to test it ?
@NoxInmortus the easiest is probably to create a directory collections/ansible_collections/community/
relative to your playbook, and inside there clone this repository as network
(i.e. it is checked out as collections/ansible_collections/community/network/
, and there for example is a file collections/ansible_collections/community/network/galaxy.yml
) (if you have git installed: run git clone https://github.com/ansible-collections/community.network.git network
in the collections/ansible_collections/community/
directory). When running your playbook, ansible will then use the local copy of the collection instead of the one installed. When you're done testing, you can also just delete that directory again.
Hello @felixfontein,
it did not work but I had more details in the stderr and it seems that the root of my problem was a DNS issue. After fixing it and testing my playbook again with the latest release (and not the current master branch), it worked as well.
Resolved then.
thanks for the help
@NoxInmortus I'm glad it's now working for you :)
SUMMARY
Cannot connect to edgeOS 1.10.11 with network_cli
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Orchestrator is Ubuntu 20.04/python3 and host is EdgeMax Router X running edgeOS 1.10.11
STEPS TO REPRODUCE
My playbook:
EXPECTED RESULTS
Working edgeos modules
ACTUAL RESULTS