The issue encountered was due to the way in which the modules communicate to Isilon API. One of the two options are required to ensure Isilon Ansible playbook connectivity:
Edit the playbook with "connection: local", see example:
- name: Collect set of facts in Isilon hosts: isilon822dc1 connection: local
Add new Isilon host "isilon822dc1_local" with the variable "ansible_connection=local" in ansible host file or hostvars. Use the following in playbook:
- name: Collect set of facts in Isilon hosts: isilon822dc1_local
Is the Ansible instance running with a Python virtual environment (venv)? Did you double check the SDK installation location to see if the files are actually there and readable?
Another idea is to use the -vvv flag to get a lot more debug information from Ansible.
EvanKoutsandreou
4 Posts
0
June 14th, 2020 22:00
Resolved
The issue encountered was due to the way in which the modules communicate to Isilon API. One of the two options are required to ensure Isilon Ansible playbook connectivity:
Edit the playbook with "connection: local", see example:
- name: Collect set of facts in Isilon
hosts: isilon822dc1
connection: local
Add new Isilon host "isilon822dc1_local" with the variable "ansible_connection=local" in ansible host file or hostvars. Use the following in playbook:
- name: Collect set of facts in Isilon
hosts: isilon822dc1_local
bmcfeeters
1 Rookie
•
72 Posts
0
June 12th, 2020 11:00
Hey Evan,
Is the Ansible instance running with a Python virtual environment (venv)? Did you double check the SDK installation location to see if the files are actually there and readable?
Another idea is to use the -vvv flag to get a lot more debug information from Ansible.
Good luck
Bryan
bmcfeeters
1 Rookie
•
72 Posts
1
June 12th, 2020 13:00
Also that error is a result of flag being set during an attempted SDK import in the dellemc_ansible_isilon_utils.py
try:
import isi_sdk_8_1_1 as isi_sdk
from isi_sdk_8_1_1.rest import ApiException
HAS_ISILON_SDK = True
You could try doing those imports with just a regular python file and see if there is any more information sent back.
EvanKoutsandreou
4 Posts
0
June 12th, 2020 17:00
Thank-you for all your feedback
It works perfectly on CentOS 8.
I noticed the isi-sdk-8-1-1 packages are installed in different locations
CENTOS7 - /usr/lib/pythonX.X/site-packages/
CENTOS8 - /usr/local/lib/pythonX.X/site-packages/
Moving the packages to the /usr/local path did not solve the issue on CentOS7. This seems like a bug...
Has anyone else experienced a similar problem with CentOS7 and the Isilon Python SDK?
Regards,
Evan