junos_install_config causes Ansible to incorrectly report failure when warnings exist about ansible-junos-stdlib HOT 4 CLOSED

Hi Carlos,

This is related to Juniper/py-junos-eznc#358
(More issues related inside of that one)

The configuration should be be getting rolled back on module exit. Are you seeing it stay in the candidate configuration after Ansible exits?

If so, please provide the model/version.

(Your ears must have been ringing - I was just talking this morning about what you said at Nanog)

Thanks,
-Rick

from ansible-junos-stdlib.

Hi Rick,

The config was actually committed. This is a:

Model: qfx3500s
JUNOS Base OS boot [13.2X51-D30.4]

from ansible-junos-stdlib.

Thank you for the report.

This is a bug. When the exception is hit we need to rollback and unlock.

Note - this will prevent a configuration with warnings from being committed as per the other issues.

Thanks,
-Rick

from ansible-junos-stdlib.

Interestingly, Ansible only shows errors sometimes. Other times, the configuration is committed and an exception is not thrown, although the netconf logs do show the warning.

from ansible-junos-stdlib.