Set commands now failing on junos_install_config

In previous versions of junos_install_config this style of playbook would succeed. This playbook running against an vsrx in eve-ng.

---
- name: Juniper New Out of Box
  hosts: srx
  gather_facts: false
  connection: local

  tasks:
    
  - junos_install_config:
      file: "~/local_ansible/config.set"
      mode: telnet
      user: root
      port: 32781
      host: 10.0.254.1

This now fails under an updated version with the following. The full traceback is:

Traceback (most recent call last):
  File "/tmp/ansible_8olY8M/ansible_module_junos_install_config.py", line 1127, in <module>
    main()
  File "/tmp/ansible_8olY8M/ansible_module_junos_install_config.py", line 750, in main
    config_format_choices = juniper_junos_common.CONFIG_FORMAT_CHOICES
AttributeError: 'NoneType' object has no attribute 'CONFIG_FORMAT_CHOICES'

fatal: [vsrx]: FAILED! => {
    "changed": false, 
    "failed": true, 
    "module_stderr": "Traceback (most recent call last):\n  File \"/tmp/ansible_8olY8M/ansible_module_junos_install_config.py\", line 1127, in <module>\n    main()\n  File \"/tmp/ansible_8olY8M/ansible_module_junos_install_config.py\", line 750, in main\n    config_format_choices = juniper_junos_common.CONFIG_FORMAT_CHOICES\nAttributeError: 'NoneType' object has no attribute 'CONFIG_FORMAT_CHOICES'\n", 
    "module_stdout": "", 
    "msg": "MODULE FAILURE", 
    "rc": 0
}

Reading the juniper_junos_config.py file shows updates in what arguments are expected. I have tried interpreting this and changed the playbook as:

  - junos_install_config:
      load: "override"
      src: "config.set"
      format: "set"
      mode: 'telnet'
      user: root
      port: 32781
      host: 10.0.254.1

Yet the same error persists. It would be nice to get some direction this. Thanks team!

[stacywsmith]

@crosson

I’m sorry I didn’t notice this earlier. This appears to be an installation issue with the new modules. The new modules use a library of shared code which doesn’t appear to be installed on your machine.

Unfortunately, I believe this is likely an issue with the ansible-galaxy command. It doesn’t handle upgrades cleanly. Please uninstall the modules, and then install cleanly with:

sudo ansible-galaxy remove Juniper.junos
sudo ansible-galaxy install git+https://github.com/Juniper/ansible-junos-stdlib.git,,Juniper.junos

Once this is done, you can confirm that the shared library of code exists by checking for the following file:

<roles_dir>/Juniper.junos/module_utils/juniper_junos_common.py

Note: <roles_dir> is usually /etc/ansible/roles could be different on your machine.

I successfully used the following playbook successfully when trying to replicate your issue:

---
- name: 'Replicate issue #308'
  hosts: junos-all
  connection: local
  gather_facts: no
  roles:
    - Juniper.junos

  tasks:
    - name: 'Replicate issue #308'
      junos_install_config:
        file: "./config.set"
        host: "{{ jaccess.console_ts }}"
        port: "{{ jaccess.console_port }}"
        mode: telnet
        user: root
      register: response
    - name: 'Print result'
      debug:
        var: response

If you wish to update to the new module name and argument syntax, you can also use this equivalent playbook:

---
- name: 'Replicate issue #308'
  hosts: junos-all
  connection: local
  gather_facts: no
  roles:
    - Juniper.junos

  tasks:
    - name: 'Replicate issue #308'
      juniper_junos_config:
        load: 'set'
        src: './config.set'
        host: '{{ jaccess.console_ts }}'
        port: '{{ jaccess.console_port }}'
        mode: telnet
        user: root
      register: response
    - name: 'Print result'
      debug:
        var: response

If you still have issues after cleanly installing the modules, please provide the version of Ansible you are using, and the version of PyEZ you are using.

[achhabr1]

I am facing the same issue. I have opened up a new bug on this.