junos_shutdown - XMLSyntaxError' object has no attribute 'rsp

[infectedgti]

Hi,
I received an error when I run this script on QFX10002 :

---
#Playbook pour redémarrer SD-SRV-C012-2
- name: Reboot devices running Junos OS
  hosts: SD-SRV-C012-2
  roles:
  - Juniper.junos    
  connection: local
  gather_facts: no

  vars:
    restart: 'yes'
    reboot_wait: 300
  vars_prompt:
  - name: shutdown
    prompt: "Enter 'shutdown' to continue"
    private: no

  tasks:
  - name: Checking NETCONF connectivity
    wait_for: host={{ inventory_hostname }} port=830 timeout=5

  - name: Reboot de SD-SRV-C012-2
    junos_shutdown:
      user={{ juniper_user }}
      ssh_private_key_file={{ juniper_ssh_private_key_file }}
      host={{ inventory_hostname }}
      shutdown={{ shutdown }}
      reboot={{ restart }}
    register: sd_result
    notify:
    - pause_for_reboot
    - wait_reboot

  handlers:
  - name: pause_for_reboot
    pause: seconds=70
    when: sd_result.reboot == true
  - name: wait_reboot
    wait_for: host={{ inventory_hostname }} port=830 timeout={{ reboot_wait }}
    when: sd_result.reboot == true

fatal: [SD-SRV-C012-2]: FAILED! => {
    "changed": false,
    "failed": true,
    "invocation": {
        "module_args": {
            "at": null,
            "host": "SD-SRV-C012-2",
            "in_min": "0",
            "mode": null,
            "passwd": null,
            "port": "830",
            "reboot": true,
            "shutdown": "shutdown",
            "ssh_private_key_file": "/root/.ssh/id_rsa",
            "user": "ansible"
        }
    },
    "msg": "error during device reboot or shutdown SD-SRV-C012-2: 'XMLSyntaxError' object has no attribute 'rsp'"

No problem with EX4600.

Thank you for you help

[stacywsmith]

@infectedgti Can you please share the version of Junos that you are using on both the QFX10002 where you are seeing this problem and on the EX4600 where you are not seeing this problem?

[infectedgti]

Hi, please find the version below:

root@SC-C012-2> show version
re0:
--------------------------------------------------------------------------
Hostname: SC-C012-2
Model: qfx10002-36q
Junos: 15.1X53-D62.5

root@SD-TST-C012-1> show version
fpc0:
--------------------------------------------------------------------------
Hostname: SD-TST-C012-1
Model: ex4600-40f
Junos: 14.1X53-D40.8

[infectedgti]

Hello, do you have somes news/solutions ?
Thank you

[vnitinv]

@infectedgti This issue need to be fixed from underlying PyEZ. Will keep you posted once we have code changes with respect to this.

[stacywsmith]

I have attempted to workaround this issue in the new juniper_junos_system module.

An example playbook for performing a reboot is:

---
- name: 'Perform a reboot'
  hosts: junos-all
  connection: local
  gather_facts: no
  roles:
    - Juniper.junos

  tasks:
    - name: 'Perform a reboot'
      juniper_junos_system:
        action: 'reboot'
      register: response
    - name: 'Print result'
      debug:
        var: response

This may not work around all instances of this Junos problem. If you are still seeing this issue, after trying the above playbook, please work with JTAC to address the Junos issue.