Comments (4)
The PyEz connection seems to be working fine in both scenarios with and without the IdentiryFile option.
Below is the playbook used:
---
- name: “Get Device Facts”
hosts: all
collections:
- juniper.device
connection: juniper.device.pyez
gather_facts: no
tasks:
- name: “Retrieve facts from device running Junos OS”
juniper.device.facts:
savedir: "{{ playbook_dir }}"
config_format: "xml"
register: result
- debug:
var: result
~/.ssh/config file:
Host test
HostName <ip>
#IdentityFile ~/.ssh/id_rsa.pub
Playbook Result:
TASK [debug] *************************************************************************************************************************************************************************************************************************************************
task path: /root/ansible_get_unresolved_route/ansible-junos-stdlib/tests/issue626.yml:17
Loading collection ansible.netcommon from /root/.ansible/collections/ansible_collections/ansible/netcommon
<ip> attempting to start connection
<ip> using connection plugin juniper.device.pyez
Found ansible-connection at path /root/ansible_get_unresolved_route/venv/bin/ansible-connection
<1ip> found existing local domain socket, using it!
<ip> Creating device parameters: {'port': 22, 'host': '<ip>', 'user': 'xyz', 'passwd': 'NOT_LOGGING_PARAMETER', 'ssh_private_key_file': None, 'ssh_config': None, 'timeout': 30}
<ip> Opening device.
<ip> Device opened.
<ip> Setting default device timeout to 30.
<ip> created pyez connection type
<ip> Loading collection ansible.builtin from
<ip> local domain socket path is /root/.ansible/pc/841c49e4b1
ok: [test] => {
"result": {
"ansible_facts": {
"junos": {
"HOME": "/root",
"RE0": {
"last_reboot_reason": "Router rebooted after a normal shutdown.",
"mastership_state": "master",
"model": "RE-S-1800x4",
"status": "OK",
"up_time": "10 days, 16 hours, 42 minutes, 34 seconds"
},
"RE1": {
"last_reboot_reason": "Router rebooted after a normal shutdown.",
"mastership_state": "backup",
"model": "RE-S-1800x4",
"status": "OK",
"up_time": "34 days, 10 hours, 30 minutes, 39 seconds"
},
"RE_hw_mi": false,
Host test
HostName 10.209.8.59
IdentityFile ~/.ssh/id_rsa.pub
TASK [debug] *************************************************************************************************************************************************************************************************************************************************
task path: /root/ansible_get_unresolved_route/ansible-junos-stdlib/tests/issue626.yml:17
Loading collection ansible.netcommon from /root/.ansible/collections/ansible_collections/ansible/netcommon
<ip> attempting to start connection
<ip> using connection plugin juniper.device.pyez
Found ansible-connection at path /root/ansible_get_unresolved_route/venv/bin/ansible-connection
<ip> found existing local domain socket, using it!
<ip> Creating device parameters: {'port': 22, 'host': '<ip>', 'user': 'xyz', 'passwd': 'NOT_LOGGING_PARAMETER', 'ssh_private_key_file': None, 'ssh_config': None, 'timeout': 30}
<ip> Opening device.
<ip> Device opened.
<ip> Setting default device timeout to 30.
<ip> created pyez connection type
<ip> Loading collection ansible.builtin from
<ip> local domain socket path is /root/.ansible/pc/7024d9c693
ok: [test] => {
"result": {
"ansible_facts": {
"junos": {
"HOME": "/root",
"RE0": {
"last_reboot_reason": "Router rebooted after a normal shutdown.",
"mastership_state": "master",
"model": "RE-S-1800x4",
"status": "OK",
"up_time": "10 days, 16 hours, 45 minutes, 19 seconds"
},
"RE1": {
"last_reboot_reason": "Router rebooted after a normal shutdown.",
"mastership_state": "backup",
"model": "RE-S-1800x4",
"status": "OK",
"up_time": "34 days, 10 hours, 33 minutes, 20 seconds"
},
"RE_hw_mi": false,
Kindly check if the issue is still appearing.
from ansible-junos-stdlib.
Hi @p3rdu
We are not able to replicate this issue with the given information .
Could you please provide the steps in detail along with commands used for generating the rsa keys , to replicate this issue .
Thank you
from ansible-junos-stdlib.
Hi @p3rdu We are not able to replicate this issue with the given information . Could you please provide the steps in detail along with commands used for generating the rsa keys , to replicate this issue .
Thank you
Unfortunately we've moved on from Junos to SONiC NOS based switches, so I cannot provide any details regarding this case anymore.
from ansible-junos-stdlib.
Thank you for reporting the issue. However, we were unable to replicate it and therefore will close the case. @p3rdu
from ansible-junos-stdlib.
Related Issues (20)
- Get facts and printing them results in invalid or malformed argument Error HOT 2
- Executing RPC with filters returns The error was: AttributeError: 'JuniperJunosModule' object has no attribute '_check_type_dict' HOT 3
- Address readthedocs upcoming changes HOT 3
- Ansible RPC error with junipe.device.rpc module HOT 2
- ansible-lint violation: missing required arguments: _inventory_hostname, _module_name, _module_utils_path (warning) HOT 2
- juniper.device.software - Software is downloaded for each RE when using remote_package HOT 8
- Feature Request: Add option to not discard uncommitted changes HOT 2
- sphinx-build -b html . _build/html/ fails with AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' with sphinx 7.2.6 HOT 2
- Random diff on juniper SRX device HOT 1
- Update README to clarify the status of collections vs roles HOT 1
- Update tests to cover all modules, when using pyez connection plugin HOT 1
- All modules fail since Ansible 2.15.9 or >=2.16.3 ("missing required arguments") HOT 9
- Juniper's galaxy module download fails. HOT 1
- juniper.device.config always performs a commit confirmed operation HOT 13
- juniper.device.config does not transmit the error message with juniper.device.pyez connection HOT 2
- juniper.device.jsnapy fails with config_file option and juniper.device.pyez HOT 1
- juniper.device.ping fails to handle when traffic-loss values are of type float - msg: 'Packet loss 33.3333 not an integer HOT 1
- <unknown>:1813: SyntaxWarning: invalid escape sequence '\*' emitted during ansible-playbook execution HOT 1
- juniper.device.jsnapy - save the name of the failed tests to a dest_dir path . HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ansible-junos-stdlib.