Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When tried to run configuring ntp task twice, second time also, 'changed' value is shown as 1 #16

Open
tanmayx opened this issue Jul 10, 2017 · 1 comment

Comments

@tanmayx
Copy link

tanmayx commented Jul 10, 2017

Execute the task twice -

tasks:
    - name: configure ntp servers
      cisco_imc_ntp:
        state: present
        ntp_servers:
          - {'id': '1', 'ip': '1.1.1.1'}
          - {'id': '2', 'ip': '2.2.2.2'}
          - {'id': '3', 'ip': '3.3.3.3'}
        ip: '{{ imc_ip }}'
        username: '{{ imc_username }}'
        password: '{{ imc_password }}'

After running the second time, below is the output -

ansible-playbook -i inventory create_config/test_create_ntp.yml 

PLAY [imc] **********************************************************************************************************************************************

TASK [Gathering Facts] **********************************************************************************************************************************
ok: [classic_imc16]

TASK [configure ntp servers] ****************************************************************************************************************************
changed: [classic_imc16]

PLAY RECAP **********************************************************************************************************************************************
classic_imc16              : ok=2    changed=1    unreachable=0    failed=0 

The changed value should be 0 and not 1.

@tanmayx tanmayx changed the title When tried to run configuring ntp task twice, second time also changed is shown as 1 When tried to run configuring ntp task twice, second time also, 'changed' value is shown as 1 Jul 10, 2017
@tanmayx
Copy link
Author

tanmayx commented Jul 12, 2017

NOTE: This happens only when we try to configure any 3 servers and not all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant