junos_get_facts: On a dual RE, junos_get_facts module fails after a RE switchover

[mamathac]

Module: junos_get_facts
Host Model: mx480.

Steps to reproduce:

1. On a dual RE router, run an ansible playbook which consists of below code.
2. Verify that the playbook results for Get Junos Facts is fine.
3. Now issue an RE switchover and wait for the device to restore master/backup RE.
4. Run the playbook again after the switchover. Shows below error.

Playbook:

• name: Junos OS version
  hosts: all
  connection: local
  gather_facts: no

  tasks:

  • include: task_check_nc
  • name: Get Junos Facts
    junos_get_facts:
    host={{ inventory_hostname }}
    register: junos

---

Playbook result when re0 is the master and re1 is backup:

regress@vm-nomadic-ubuntu:~/ansible_junos/mydir_ansible$ ansible-playbook pb/facts --limit andrina -v

PLAY [Junos OS version] *******************************************************

TASK: [checking NETCONF] ******************************************************
ok: [andrina] => {"changed": false, "elapsed": 0, "item": "", "path": null, "port": 830, "search_regex": null, "state": "started"}

TASK: [Get Junos Facts] *******************************************************
ok: [andrina] => {"changed": false, "facts": {"2RE": true, "HOME": "/var/home/regress", "RE0": {"last_reboot_reason": "Router rebooted after a normal shutdown.", "mastership_state": "master", "model": "RE-S-1800x4", "status": "OK", "up_time": "7 days, 23 minutes, 36 seconds"}, "RE1": {"last_reboot_reason": "Router rebooted after a normal shutdown.", "mastership_state": "backup", "model": "RE-S-1800x4", "status": "OK", "up_time": "7 days, 23 minutes, 50 seconds"}, "domain": "englab.juniper.net", "fqdn": "andrina.englab.juniper.net", "hostname": "andrina", "ifd_style": "CLASSIC", "master": "RE0", "model": "MX480", "personality": "MX", "serialnumber": "JN10FE440AFB", "switch_style": "BRIDGE_DOMAIN", "version": "12.1-20140402.0", "version_RE0": "12.1-20140402.0", "version_RE1": "12.1-20140402.0"}}

PLAY RECAP ********************************************************************
andrina : ok=2 changed=0 unreachable=0 failed=0

---

Playbook result when master is re1 and backup is re0:

regress@vm-nomadic-ubuntu:~/ansible_junos/mydir_ansible$ ansible-playbook pb/facts --limit andrina -v

PLAY [Junos OS version] *******************************************************

TASK: [checking NETCONF] ******************************************************
ok: [andrina] => {"changed": false, "elapsed": 0, "item": "", "path": null, "port": 830, "search_regex": null, "state": "started"}

TASK: [Get Junos Facts] *******************************************************
failed: [andrina] => {"failed": true, "parsed": false}
invalid output was: Traceback (most recent call last):
File "/home/regress/.ansible/tmp/ansible-tmp-1397213264.56-247484810680075/junos_get_facts", line 1305, in
main()
File "/home/regress/.ansible/tmp/ansible-tmp-1397213264.56-247484810680075/junos_get_facts", line 95, in main
dev.open()
File "/usr/local/lib/python2.7/dist-packages/jnpr/junos/device.py", line 247, in open
self.facts_refresh()
File "/usr/local/lib/python2.7/dist-packages/jnpr/junos/device.py", line 412, in facts_refresh
gather(self, self._facts)
File "/usr/local/lib/python2.7/dist-packages/jnpr/junos/facts/chassis.py", line 28, in chassis
facts['model'] = x_ch.find('description').text
AttributeError: 'NoneType' object has no attribute 'find' >>>>ERROR

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************
to retry, use: --limit @/home/regress/facts.retry

andrina : ok=1 changed=0 unreachable=0 failed=1

---

Expected Result

Junos get facts should return the device information after the switchover without errors.

[jeremyschulman]

@mamathac - please login to the master "re1" and confirm a few things:

1. Does the MX dual-RE system have a shared IP address on fxp0 in the [groups re0] and [groups re1] stanza - or are there different IP addresses exlusively?

2. When you login to the master, can you do a "show chassis hardware" command and determine if there is a chassis/description provided?

Thank you!

[jeremyschulman]

@mamathac - also, this bug relates to the underlying py-junos-eznc library, and not specifically to the ansible modules. I will see if I can administratively move this issue to that repo.

For future issues, please consider whether the bug is specific to the ansible module or to the underlying py-junos-eznc library. If you have any questions, you can email me directly before opening the issue. Thank you!

[mamathac]

@jeremyschulman
At the master (re1):

1. Does the MX dual-RE system have a shared IP address on fxp0 in the [groups re0] and [groups re1] stanza - or are there different IP addresses exlusively?

Both groups share the same IP:
set groups re0 system host-name andrina
set groups re0 system backup-router 10.209.63.254
set groups re1 system host-name andrina1
set groups re1 system backup-router 10.209.63.254

2. When you login to the master, can you do a "show chassis hardware" command and determine if there is a chassis/description provided?
   Yes, There is hardware description when I "issue show chassis hardware". Here is the output.

regress@andrina1> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis JN10FE440AFB MX480
Midplane REV 05 710-017414 TR4162 MX480 Midplane
FPM Board REV 02 710-017254 WR5976 Front Panel Display
PEM 1 Rev 03 740-017330 QCS0812904H PS 1.2-1.7kW; 100-240V AC in
PEM 2 Rev 03 740-017330 QCS08129047 PS 1.2-1.7kW; 100-240V AC in
PEM 3 Rev 03 740-017330 QCS0812901J PS 1.2-1.7kW; 100-240V AC in
Routing Engine 0 REV 07 740-031116 9009118478 RE-S-1800x4
Routing Engine 1 REV 07 740-031116 9009118475 RE-S-1800x4
CB 0 REV 11 710-021523 ZM0541 MX SCB
CB 1 REV 14 710-021523 WR3827 MX SCB
FPC 1 REV 07 750-018122 WR7148 DPCE 40x 1GE R
CPU REV 06 710-013713 WS6391 DPC PMB
PIC 0 BUILTIN BUILTIN 10x 1GE(LAN)
Xcvr 0 REV 02 740-011613 PKC0HZP SFP-SX
Xcvr 1 REV 02 740-011613 PKC0TA2 SFP-SX
Xcvr 2 REV 02 740-011613 PKC1796 SFP-SX
Xcvr 3 REV 02 740-011613 PKC0TCP SFP-SX
Xcvr 4 REV 02 740-011613 PKC16KQ SFP-SX
Xcvr 5 REV 02 740-011613 PKC0SD1 SFP-SX
Xcvr 6 REV 02 740-011613 PKC0GV4 SFP-SX
Xcvr 7 REV 02 740-011613 PKC0TNN SFP-SX
Xcvr 8 REV 02 740-011613 AM0943SEJL7 SFP-SX
Xcvr 9 REV 01 740-031851 PP20FU7 SFP-SX
PIC 1 BUILTIN BUILTIN 10x 1GE(LAN)
Xcvr 1 REV 01 740-031851 PP21CM6 SFP-SX
Xcvr 2 REV 01 740-031851 PLB113U SFP-SX
Xcvr 3 REV 01 740-031851 AC1202S00SQ SFP-SX
Xcvr 4 REV 01 740-031851 PP20XNC SFP-SX
Xcvr 5 REV 01 740-031851 PLB0QHN SFP-SX
Xcvr 6 REV 01 740-011613 PDL04LS SFP-SX
Xcvr 7 REV 01 740-011613 PDD41LP SFP-SX
PIC 2 BUILTIN BUILTIN 10x 1GE(LAN)
Xcvr 4 REV 01 740-031851 PP21CMC SFP-SX
Xcvr 5 REV 01 740-031851 PLB24SE SFP-SX
Xcvr 6 REV 01 740-031851 PLB25D9 SFP-SX
Xcvr 8 REV 01 740-031851 PMF302U SFP-SX
Xcvr 9 REV 01 740-031851 PMF15QC SFP-SX
PIC 3 BUILTIN BUILTIN 10x 1GE(LAN)
FPC 2 REV 29 750-022765 CAAZ5990 DPCE 20x 1GE + 2x 10GE R
CPU REV 05 710-022351 CAAZ5159 DPC PMB
PIC 0 BUILTIN BUILTIN 10x 1GE(LAN)
Xcvr 0 REV 01 740-011613 PD63DCW SFP-SX
Xcvr 1 REV 01 740-011613 PDL07BL SFP-SX
Xcvr 2 REV 01 740-031851 AC1047S04WT SFP-SX
Xcvr 3 REV 01 740-031851 AC1047S04X6 SFP-SX
PIC 1 BUILTIN BUILTIN 10x 1GE(LAN)
PIC 2 BUILTIN BUILTIN 1x 10GE(LAN/WAN)
Xcvr 0 REV 03 740-014289 CD02BQ139 XFP-10G-SR
PIC 3 BUILTIN BUILTIN 1x 10GE(LAN/WAN)
Xcvr 0 REV 03 740-014289 CD09BQ0BK XFP-10G-SR
FPC 3 REV 38 750-016670 YY0224 DPCE 40x 1GE R EQ
CPU REV 08 710-013713 YX0087 DPC PMB
PIC 0 BUILTIN BUILTIN 10x 1GE(LAN) EQ
Xcvr 9 REV 02 740-013111 C029238 SFP-T
PIC 1 BUILTIN BUILTIN 10x 1GE(LAN) EQ
PIC 2 BUILTIN BUILTIN 10x 1GE(LAN) EQ
Xcvr 9 REV 02 740-013111 B388772 SFP-T
PIC 3 BUILTIN BUILTIN 10x 1GE(LAN) EQ
FPC 4 REV 14 750-024387 YZ6590 MX FPC Type 2
CPU REV 04 710-022351 YX4709 DPC PMB
PIC 1 REV 13 750-011800 ZR0967 8x 1GE(LAN), IQ2
Fan Tray Left Fan Tray

regress@andrina1>

[jeremyschulman]

@mamathac - closing this issue on this repo as it was reported on the py-junos-eznc repo.