Unsolved
1 Rookie
•
4 Posts
0
60
March 27th, 2025 15:15
Powerscale Ansible Module compatibility issues
Hello All,
I am new to Ansible and I am trying to automate some cluster configurations.
But when I am running the playbook getting an error that the python module on the Powerscale cluster is not yet supported by the module.
I have followed all the pre-requistes as mentioned in the documentation but I am getting an error that the python version on the Powerscale cluster is not supported by the Ansible module.
Please find the below setup -
Ansible control node - RHEL 9.5
Powerscale OneFS - 9.4.0.16 and 9.7.1.2 (Tested on both)
Ansible Core -
[root@localhost karthiklal]# ansible --version
ansible [core 2.15.0]
config file = /home/karthiklal/ansible.cfg
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.11/site-packages/ansible
ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/local/bin/ansible
python version = 3.11.9 (main, Dec 9 2024, 00:00:00) [GCC 11.5.0 20240719 (Red Hat 11.5.0-2)] (/usr/bin/python3.11)
jinja version = 3.1.6
libyaml = True
Python - 3.11.9
Ansible Powerscale Module - 3.7.0
Isilon SDK -
isilon-sdk 0.3.0.1
[root@localhost karthiklal]# ansible-playbook -i inventory-pscale playbook-pscale.yaml
PLAY [Get SMB share details] ****************************************************************************************************************************************************************************************************************
TASK [Gathering Facts] **********************************************************************************************************************************************************************************************************************
[WARNING]: Platform isilon onefs on host 10.241.217.215 is using the discovered Python interpreter at /usr/local/bin/python3.8, but future installation of another Python interpreter could change the meaning of that path. See
https://docs.ansible.com/ansible-core/2.18/reference_appendices/interpreter_discovery.html for more information.
ok: [10.241.217.215]
TASK [Get email settings] *******************************************************************************************************************************************************************************************************************
fatal: [10.241.217.215]: FAILED! => {"changed": false, "msg": "Python version 3.8.19 is not yet supported by this module. Please refer the support metrics for more information."}
PLAY RECAP **********************************************************************************************************************************************************************************************************************************
10.241.217.215 : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
[root@localhost ]# cat playbook-pscale.yaml
---
- name: Get SMB share details
hosts: all
collections:
- dellemc.powerscale
tasks:
- name: Get email settings
dellemc.powerscale.settings:
onefs_host: "***********"
api_user: "root"
api_password: "************"
verify_ssl: "false"
state: "present"
- name: Gddet SMB share details
dellemc.powerscale.smb:
onefs_host: "*********"
verify_ssl: "false"
api_user: "root"
api_password: "********"
share_name: "target"
state: "present"