Closed coloradokb closed 11 months ago
anupamaloke
commented
11 months ago @coloradokb, could you please share the output of your playbook run with verbosity turned on (-vvv)?
Also just checking on whether you might have different python version installed on your box? If yes, then one of ways to make sure that you are using the right python binary is by setting the ansible_python_interpreter variable to correct python path. For e.g.
ansible_python_interpreter: "/usr/bin/env python"
Javedkhansiddiqui
commented
11 months ago I think you can find some solution here
Unable-to-import-PowerScale-python-library-Please-install-isilon
With the latest ansible module release, the installation of SDK is isilon-sdk(which can be installed using pip3 install isilon-sdk for all versions of onefs instead of version specific sdk installation as in previous releases. Please do let me know of any further clarifications
anupamaloke
commented
11 months ago @coloradokb, I will be closing this issue. If you are still running into same error, please feel free to create a new issue or reopen this one.
coloradokb
commented
11 months ago Sorry for my lack of response and thank you for the feedback. Turns out the fix in my env was 2-fold.
Thank again!
anupamaloke
commented
11 months ago Sorry for my lack of response and thank you for the feedback. Turns out the fix in my env was 2-fold.
- pip install of sdk; specifically isilon-sdk==0.3.0
- ansible_python_interpreter=venv/bin/python3
Thank again!
Brilliant! Glad that you were able to get it fixed.
How can the Team help you today?
I'm trying to understand what I could have done, but seemingly out of nowhere, I'm receiving the follower error when running a playbook. Have tried multiple modules (accesszone, filesystem, etc) and receiving:
Unable to import PowerScale python library. Please install isilon-sdk. Please install the required package(s)I have reinstalled isi-sdk-9-1-0 and isi-sdk-8-1-0 and isilon-sdk to no avail. I'm 99% sure I am correctly setting the ANSIBLE_COLLECTIONS_PATHS path too and verifying correct python3 is being used.
Anyone else seeing this? Thanks!!!