Closed rawstorage closed 1 year ago
@rawstorage, thank you for submitting this. We will add this to the backlog, triage and add a release milestone when available.
Thanks Anupam, note there are also some case sensitivity issues around Host and HostGroup names, this should also be addressed in the fix
Closing this issue as it is fixed as part of PR #28
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
host_flags: consistent_lun: true state: 'present' initiators: "{{ item.initiators}}" initiator_state: 'present-in-host' register: childIgCreateResponse loop: "{{ hosts }}" ... hosts:
n. Step n See error
failed: [localhost] (item={'name': 'REGTESTESX041', 'initiators': ['3311111111111EA2', '3311111111111EA3']}) => {"ansible_loop_var": "item", "changed": false, "item": {"initiators": ["3311111111111EA2", "3311111111111EA3"], "name": "REGTESTESX041"}, "msg": "Adding initiators ['3311111111111EA2', '3311111111111EA3'] to host IG_REGTESTESX041 failed with error Bad or unexpected response from the storage volume backend API: Error PUT symmetrix resource. The status code received is 500 and the message is {'message': 'A problem occurred modifying the host resource: Error for: 000297900442/IG_REGTESTESX041: The operation can not be performed because the group is already in this state'}."} failed: [localhost] (item={'name': 'REGTESTESX042', 'initiators': ['3311111111111EA4', '3311111111111EA5']}) => {"ansible_loop_var": "item", "changed": false, "item": {"initiators": ["3311111111111EA4", "3311111111111EA5"], "name": "REGTESTESX042"}, "msg": "Adding initiators ['3311111111111EA5', '3311111111111EA4'] to host IG_REGTESTESX042 failed with error Bad or unexpected response from the storage volume backend API: Error PUT symmetrix resource. The status code received is 500 and the message is {'message': 'A problem occurred modifying the host resource: Error for: 000297900442/IG_REGTESTESX042: The operation can not be performed because the group is already in this state'}."}
Expected behavior Module should not care about case, WWN should be normalised on API side to match for idempotency regardless of upper|lower this is the behaviour in PowerMax CLI
Screenshots If applicable, add screenshots to help explain your problem.
Logs If applicable, submit logs or stack traces from the affected services
System Information (please complete the following information):
Additional context Add any other context about the problem here.