
Solved!
Go to SolutionClosed
Powerscale Ansible: LDAP Module not Idempotent
Hi @jennifer_john,
Whenever I run the below code, I get a "changed" instead of an "ok" after the LDAP Provider is already created
- name: Create LDAP Provider
dellemc.powerscale.ldap:
onefs_host: "{{ inventory_hostname }}"
port_no: "{{ isilon_port }}"
verify_ssl: false
api_user: "{{ isilon_user }}"
api_password: "{{ isilon_password }}"
ldap_name: "{{ team.name }}"
server_uris: "{{ team.ldap.server_uris }}"
server_uri_state: "{{ team.ldap.server_uri_state }}"
base_dn: "{{ base_dn }}"
ldap_parameters:
groupnet: "{{ groupnet }}"
state: "present"
register: out_ldap
delegate_to: "{{ groups['storage_server'][0] }}"thanks.
glenn.
Responses (5)
Solutions (0)
jennifer_john
1 Rookie
•
79 Posts
857
0
Posted April 26th, 2023 10:00
Hi @gdny
Could you share the output of tail -10 ansible_powerscale.log on executing idempotent task since Idempotency seem to work
Thanks,
Jennifer
Hi @jennifer_john
The below excerpt includes a few other tasks, but the:2023-04-26 13:38:07,536 ldap.py INFO : LDAP provider updated successfully.
constantly repeats every time I run the playbook.
2023-04-26 13:30:31,761 info.py INFO : Got Nodes from PowerScale cluster mt72management.mtisilon72.saccap.int 2023-04-26 13:35:16,100 info.py INFO : Got python SDK instance for provisioning on PowerScale 2023-04-26 13:35:24,248 info.py INFO : Got Nodes from PowerScale cluster mt72management.mtisilon72.saccap.int 2023-04-26 13:37:19,878 ldap.py INFO : Got the isi_sdk instance for authorization on to PowerScale 2023-04-26 13:37:19,955 ldap.py INFO : Modifying LDAP provider. 2023-04-26 13:37:20,166 ldap.py INFO : LDAP provider updated successfully. 2023-04-26 13:37:22,337 accesszone.py INFO : Got the isi_sdk instance for authorization on to PowerScale 2023-04-26 13:37:22,911 accesszone.py INFO : added auth providers to access zone 2023-04-26 13:37:24,610 accesszone.py INFO : Got the isi_sdk instance for authorization on to PowerScale 2023-04-26 13:37:25,438 accesszone.py INFO : removed auth providers from access zonethanks.
glenn.jennifer_john
1 Rookie
•
79 Posts
824
0
Posted April 28th, 2023 06:00
Hi @gdny
I have shared the steps to add additional log statements in ldap.py to capture logging, as I could not share the updated module file over email.
Could you please share the updated logs or let me know if a webex would help too
Thanks,
Jennifer.
Hi @jennifer_john,
Sorry it took so long to get back to you. I ran the command a few time:
[svcansible@prd22emcsvcs01 ~]$ tail -10 ansible_powerscale.log 2023-05-01 15:42:36,321 ldap.py INFO : {'bind_dn': None} 2023-05-01 15:42:36,633 ldap.py INFO : LDAP provider updated successfully. 2023-05-01 15:42:40,886 ldap.py INFO : Got the isi_sdk instance for authorization on to PowerScale 2023-05-01 15:42:40,971 ldap.py INFO : Modifying LDAP provider. 2023-05-01 15:42:40,971 ldap.py INFO : {'bind_dn': None} 2023-05-01 15:42:41,154 ldap.py INFO : LDAP provider updated successfully. 2023-05-01 15:42:44,832 ldap.py INFO : Got the isi_sdk instance for authorization on to PowerScale 2023-05-01 15:42:44,908 ldap.py INFO : Modifying LDAP provider. 2023-05-01 15:42:44,908 ldap.py INFO : {'bind_dn': None} 2023-05-01 15:42:45,091 ldap.py INFO : LDAP provider updated successfully.Let me know if you need anything else.
thanks
glenn.

jennifer_john
1 Rookie
•
79 Posts
748
0
Posted May 3rd, 2023 11:00
Hi @gdny
Thank you for sharing the updated logs, This is a defect, we will work on fixing it in the upcoming release. I have also shared the fix over email for verification.
Thanks,
Jennifer