ios_config: ansible 2.5.2 idempotency issue/bug? #40064
Labels
affects_2.5
This issue/PR affects Ansible v2.5
bug
This issue/PR relates to a bug.
cisco
Cisco technologies
ios
Cisco IOS community
module
This issue/PR relates to a module.
networking
Network category
support:network
This issue/PR relates to code supported by the Ansible Network Team.
ISSUE TYPE
COMPONENT NAME
ios_config
ANSIBLE VERSION
CONFIGURATION
DEFAULT_FORKS(/etc/ansible/ansible.cfg) = 10
DEFAULT_HOST_LIST(/etc/ansible/ansible.cfg) = [u'/etc/ansible/inventory']
DEFAULT_ROLES_PATH(/etc/ansible/ansible.cfg) = [u'/etc/ansible/roles']
HOST_KEY_CHECKING(/etc/ansible/ansible.cfg) = False
PARAMIKO_HOST_KEY_AUTO_ADD(/etc/ansible/ansible.cfg) = True
PERSISTENT_CONNECT_TIMEOUT(/etc/ansible/ansible.cfg) = 30
OS / ENVIRONMENT
Running Ansible from Centos 7.2 and testing ios_config module on a Cisco IOS device running version:
15.2(2)E3
SUMMARY
I am testing Ansible version 2.5.2 to push snmp changes to a Cisco IOS network device. I am only doing a simple command "snmp-server community Test1ng RW" and running the playbook. Despite Ansible pushing the change successfully and the device having it in running-config, Ansible still tries to change configuration again. When doing changes with large configuration files, this is causing a confusion as I don't really know if something got changed in my ansible configuration.
I don't see this issue in Ansible version 2.4.2.0.
STEPS TO REPRODUCE
EXPECTED RESULTS
Ansible should make the change only for the first time and should not change end device anymore.
ACTUAL RESULTS
If I run the playbook again (the playbook output is showing "changed" everytime I run the playbook (even though the end device has the desired configuration). I logged into the device and noticed that Ansible is trying to push the command every single time.
The text was updated successfully, but these errors were encountered: