Open mweinelt opened 1 year ago
@mweinelt This is not reproducible for me wiht vsrx18.4R1, could you please provide detailed debug logs for the failure mentioned above.You can enable detailed debug logs with
export ANSIBLE_LOG_PATH=ansible.log
export ANSIBLE_PERSISTENT_LOG_MESSAGES=TRUE
export ANSIBLE_DEBUG=TRUE
This example runs against an EX2200-C running JUNOS 12.3R12, but can also reproduce on an ACX5448 running 20.2.R3
https://gist.github.com/mweinelt/485ed63892fb99c5ef8b70a36ae0a7b7
I am reproducing the same issue against EX-3400/4300's running JUNOS 22.2R1.9 and 14.1X53-D46.7.
Task:
# For debugging purposes
- name: Juniper | Collect Facts and Configuration
run_once: true
junipernetworks.junos.junos_facts:
gather_subset: hardware
ansible.log: https://gist.github.com/TkPegatron/7860e9dee01e93b2800122f4c91874cb
Same for EX4200-48T and EX2200-48T-4G running JunOS 12.3 and 15.1. gather_subset
all
and hardware
fails, while config
, interfaces
and min
works.
I can still reproduce this issue on 6.0.0.
EX3400 with 21.4R3-S3.4
Edit: Works after installing xmltodict
, so I assume it broke in 8dc32637e61e445a6820fab7b3e668fd7e9884db.
The problem is also reproducible on 8.0.0
when fetching "hardware" data from mx10008
running 22.4R2.8
. It was also solved for me by installing xmltodict
module.
The problem is also reproducible on 9.1.0
when fetching "hardware" data. It was also solved for me by installing xmltodict
Python module.
SUMMARY
Gathering hardware facts fails with 4.1.0, is fine with 4.0.0.
ISSUE TYPE
COMPONENT NAME
junipernetworks.junos.junos
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
Linux Python 3.10.8
STEPS TO REPRODUCE
EXPECTED RESULTS
Gather hardware facts.
ACTUAL RESULTS