Runtime Error from Juniper.junos role

Archives Ansible Project
1

Hello,

I installed Ansible(2.2.1.0), the Juniper.junos(1.4.0) role from Ansible galaxy with junos-eznc (2.1.1). I tried to create a test playbook to obtain the version of my test switch as shown below.

2

I’ve resolved this. There was an update made to junos-eznc that broke the version of Juniper-junos on Ansible-Galaxy. I had to pull a more recent version from the git repo.

Daniel

3

Hi Daniel,

Would you please share how did you upgrade? I am also getting similar error.

"TASK [GET-MODEL] ***************************************************************
fatal: [192.168.56.103]: FAILED! => {“changed”: false, “failed”: true, “module_stderr”: “/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py:141: FutureWarning: CTR mode needs counter parameter, not IV\n self._cipher = factory.new(key, *args, **kwargs)\nTraceback (most recent call last):\n File "/home/yasir/.ansible/tmp/ansible-tmp-1492337992.22-261119891504603/junos_get_facts", line 2168, in \n main()\n File "/home/yasir/.ansible/tmp/ansible-tmp-1492337992.22-261119891504603/junos_get_facts", line 176, in main\n dev.facts[‘has_2RE’] = dev.facts[‘2RE’]\n File "/usr/local/lib/python2.7/dist-packages/jnpr/junos/factcache.py", line 171, in setitem\n raise RuntimeError("facts are read-only!")\nRuntimeError: facts are read-only!\n”, “module_stdout”: “”, “msg”: “MODULE FAILURE”, “parsed”: false}

PLAY RECAP *********************************************************************
192.168.56.103 : ok=0 changed=0 unreachable=0 failed=1 "

Thanks,

MYN