Closed 33Fraise33 closed 1 year ago
I've come across identical issue with the latest version. Would be nice to see it resolved.
I am also now experiencing this issue with the Juniper.Junos
role since upgrading to ansible-core>=2.13
or ansible>=6.0
. I am now stuck on ansible-core<=2.12
as I am unable to authenticate to a device as the credentials aren't being correctly obtained from the command line when authenticating using a password protected SSH public key - the ssh_private_key_file
field is being passed through as null
.
Ansible believe the solution is that the juniper plugin will need to be updated to consult self._connection.get_option()
as opposed to attempting to get the information from task_vars
.
This issue is also present with the newer juniper.device
collection for Ansible. Tested using juniper.device==1.0.2
which fails with ansible-core>=2.13
.
PR #615 raised if anyone is still actively maintaining this repository?
Hi @cmason3 Thanks , We are running functional tests .
Thanks
Fix is merged via https://github.com/Juniper/ansible-junos-stdlib/pull/615
Issue Type
Module Name
Juniper.device.config
juniper.device collection and Python libraries version
OS / Environment
Juniper EX2300 Junos: 21.2R2-S2.3
Summary
The module is not passing the ssh password from the command line /environment anymore. when you supply
--ask-pass
or-k
it does not pass it through to the juniper.device.config module. I need to supply:passwd: "{{ ansible_ssh_pass | default(omit) }}"
to have it work with password authentication on initial staging/config.Steps to reproduce
In the below config if the passwd module is removed it stops working, this was working before but I am not sure why it does not anymore without explicitely add the passwd entry.
Expected results
Use the supplied password by default instead of needing to add it to the module. Actual results