Solved
Forum Discussion
- james_wuerfleinNovice IBut this should easily be duplicatable if you point it to a self sign cert.
- simonPuritanexactly - we have never encountered these SSL messages causing a failure. We only see them when there is a real failure in the code. And I can't debug that without the traceback Let me try and replicate with your example
- james_wuerfleinNovice IPlease and thank you. I wouldnt have raised the issue otherwise, and would love to give you the full debug but just not able to currently.
- james_wuerfleinNovice IProblem is there is no option in the pure modules to turn ssl verification off. I have seen some other ones that do have that option, and maybe that is point of clarification as maybe you do that in your code and its just not exposed. Which I didn't see much in the documentation. With the python documentation I saw there was a way to do that, but had to do it more globally to ignore any errors/warnings from the python code to get it to pass the check or play.
- simonPuritanOK - so I can't reproduce this: ```$ ansible-playbook test.yaml [WARNING]: No inventory was parsed, only implicit localhost is available [WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all' PLAY [casefold host] ************************************************************************************************************************************************** TASK [Gathering Facts] ************************************************************************************************************************************************ ok: [localhost] TASK [Take Snapshot of Protetion Group of "simon"] ******************************************************************************************************************** changed: [localhost] PLAY RECAP ************************************************************************************************************************************************************ localhost : ok=2 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0``` The playbook is exactly the same as yours. Please double check the pypureclient SDK version and the Ansible Collection is at 1.28.0 (or 1.28.1 which was released today). I do not have an AAP environment to try this out on. Would you be willing to do a Zoom call to look over this?
- simonPuritanRemember that the pypureclient version can be different in the shell AAP is using if you have not ensured the playbook is using the latest version of the SDK. It is advisable to use the pip module to ensure pypureclient is at the latest version right at the start of your playbooks
- james_wuerfleinNovice Isure, I usually add those to the requirements.yaml file so they get updated.
- james_wuerfleinNovice Iand a pip install task if they are pip moduules
- simonPuritanThe current default is not to verify SSL certificates, which is why we get those warnings in traceback logs. They are benign. The modules do not have the ability to force SSL cert checking and passing an SSL cert to use. This is because the majority of arrays use self-signed certs (as you are doing). We could add this but we haven't had any specific requests for it. In your case this wouldn't have any effect.
- simonPuritanSomething else is causing the modules to fail, or appear to fail.
Related Content
- 3 months ago
- 2 months ago