Open dennym opened 1 year ago
Further inspections resulted in that there was an issue on our side but the error was not meaningful.
The SyncIQ service was not activated and unfortunately the playbook and the sdk did not catch that exception and ran into the next logic step and couldn't handle the response.
This line uses the Isilon python binding sdk and assumes that it either returns no policy or a collection of policies https://github.com/dell/ansible-powerscale/blob/master/plugins/modules/synciqpolicy.py#L500
The API call happens here: https://github.com/Isilon/isilon_sdk_python/blob/a76bec4087528b16679c54f4c9e1200a590b47bd/isi_sdk_9_1_0/isi_sdk_9_1_0/api/sync_api.py#L3033
We weren't able to check the actual response there but it should have failed and be caught.
Solution would be either to somehow check if self.api_instance.get_sync_policy(name_or_id).policies
works or returns an exception or isilon sdk needs to have some exception handling. I leave it open until some response but it basically is resolved.
Best
Thanks @dennym for reporting the issue. We will look into the scenario, if it can be handled by the module.
Thanks, Jennifer
@dennym We tried to replicate the above issue. Our setup doesn't have synciq activated as in below screenshot
But then when we executed the create workflow for the synciq from ansible we got the below result
This works as expected. Can you please share further information for us to replicate the issue.
Description We are trying to manage SyncIQ-Policies using this collection but we're running into the following issue: Unless we leave out required parameters like state or provide wrong credentials on purpose (in which case we get a "normal" Ansible error, such as "incorrect username or password"), we always get the following Python error message:
Logs
To reproduce
System Information:
Expected behavior
The "debug" policy is either deleted if it exists or nothing is done if it doesn't. In either case, the task should succeed.
Other modules from this collection such as
smb
andsmartquota
work w/o issue on the same setup.Are there any implicitely required parameters we are missing here?
Best