purefa_connect fails

[ryuyamag]

Summary
purefa_connect fails when using FlashArray Collection versions after the REST v2 transition. The same tasks work correctly with Collection 1.28.0, but fail with 1.41.0 against the same arrays.

Environment

• Ansible version: core 2.15.8
• FlashArray Collection version: 1.41.0
• Purity versions tested: 6.7.5, 6.9.1
• Module: purefa_connect
• Operation: state: present (create array connection)

With FlashArray Collection 1.28.0, the same purefa_connect task succeeds for these arrays and Purity versions. The problem appears with 1.29.0 and later.

A. Connect from Purity 6.7.5 → 6.9.1
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error"

B. Connect from Purity 6.9.1 → 6.7.5
"msg": "Array Connection failed. Error: None"

C. Connect from Purity 6.7.5 → 6.7.5
"msg": "Array Connection failed. Error: Given Transport Type is invalid"

Log files
a_675to691.txt
b_691to675.txt
c_675to675.txt

[sdodsley]

@ryuyamag please try patch #890 to see how much of your issue is resolved.
Let me know what now works and what still doesn't.
For still failing portions, send over logs

[ryuyamag]

Thank you for providing the patch.
I re‑tested the three scenarios I originally reported:

A. Connect from Purity 6.7.5 → 6.9.1
msg: "MODULE FAILURE\nSee stdout/stderr for the exact error"

B. Connect from Purity 6.9.1 → 6.7.5
msg: "Array Connection failed. Error: None"

C. Connect from Purity 6.7.5 → 6.7.5
msg: "Array Connection failed. Error: Given Transport Type is invalid"

Scenario C now appears to be resolved with the patch – the connection from 6.7.5 to 6.7.5 succeeds.
However, A and B are still in the same state as before. I’m using py-pure-client 1.81.0 for these tests. I’ve attached the latest logs for A and B for your reference.

A.675to691.txt
B.691to675.txt

[sdodsley]

@ryuyamag please try with the latest patch and let me know what happens.

[ryuyamag]

@sdodsley
Sorry for the delay.
I was able to confirm that it works with the fix you provided.