
Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
PM
pawan.mishra.devops
1 Rookie
•
1 Message
0
705
October 19th, 2020 06:00
Problem on Power max code "https://github.com/dell/ansible-powermax" with Ansible 2.10.2 with Python 3.8
We facing issue to execute "https://github.com/dell/ansible-powermax" code in Ansible 2.10.2 and Python 3.8.
Following Error is coming, Please advise.
The full traceback is:
Traceback (most recent call last):
File "/opt/rh/rh-python38/root/usr/local/lib/python3.8/site-packages/ansible/executor/task_executor.py", line 158, in run
res = self._execute()
File "/opt/rh/rh-python38/root/usr/local/lib/python3.8/site-packages/ansible/executor/task_executor.py", line 663, in _execute
result = self._handler.run(task_vars=variables)
File "/opt/rh/rh-python38/root/usr/local/lib/python3.8/site-packages/ansible/plugins/action/normal.py", line 46, in run
result = merge_hash(result, self._execute_module(task_vars=task_vars, wrap_async=wrap_async))
File "/opt/rh/rh-python38/root/usr/local/lib/python3.8/site-packages/ansible/plugins/action/__init__.py", line 861, in _execute_module
(module_style, shebang, module_data, module_path) = self._configure_module(module_name=module_name, module_args=module_args, task_vars=task_vars)
File "/opt/rh/rh-python38/root/usr/local/lib/python3.8/site-packages/ansible/plugins/action/__init__.py", line 231, in _configure_module
(module_data, module_style, module_shebang) = modify_module(module_name, module_path, module_args, self._templar,
File "/opt/rh/rh-python38/root/usr/local/lib/python3.8/site-packages/ansible/executor/module_common.py", line 1299, in modify_module
(b_module_data, module_style, shebang) = _find_module_utils(module_name, b_module_data, module_path, module_args, task_vars, templar, module_compression,
File "/opt/rh/rh-python38/root/usr/local/lib/python3.8/site-packages/ansible/executor/module_common.py", line 1139, in _find_module_utils
recursive_finder(module_name, remote_module_fqn, b_module_data, zf)
File "/opt/rh/rh-python38/root/usr/local/lib/python3.8/site-packages/ansible/executor/module_common.py", line 914, in recursive_finder
module_info = LegacyModuleUtilLocator(py_module_name, is_ambiguous=is_ambiguous,
File "/opt/rh/rh-python38/root/usr/local/lib/python3.8/site-packages/ansible/executor/module_common.py", line 753, in __init__
self._locate(redirect_first=False) # let local stuff override redirects for legacy
File "/opt/rh/rh-python38/root/usr/local/lib/python3.8/site-packages/ansible/executor/module_common.py", line 706, in _locate
if self._find_module(candidate_name_parts):
File "/opt/rh/rh-python38/root/usr/local/lib/python3.8/site-packages/ansible/executor/module_common.py", line 771, in _find_module
if info is not None and os.path.splitext(info.origin)[1] in importlib.machinery.SOURCE_SUFFIXES:
File "/opt/rh/rh-python38/root/usr/lib64/python3.8/posixpath.py", line 118, in splitext
p = os.fspath(p)
TypeError: expected str, bytes or os.PathLike object, not NoneType
fatal: [emaedcw715]: FAILED! => {
"msg": "Unexpected failure during module execution.",
"stdout": ""
Responses (4)
Solutions (0)
bmcfeeters
1 Rookie
•
72 Posts
532
0
Posted October 20th, 2020 08:00
The error that you are getting here seems to indicate that Ansible can't find the PowerMax modules. You may want to review where Ansible is looking for the modules.
[root@lglbx090 ~]# ansible --version
ansible 2.10.1
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.17 (default, Jun 5 2020, 03:38:32) [GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]Reply sassyrpri123
1 Rookie
•
1 Message
•
2 Points
1
0
Posted June 30th, 2025 09:17
Hello everyone,
I am facing the same issues and looking for a best solution. It must be working and looking forward for it. I hope i will get it from here.
Thanks
Reply matthewcolers
1 Rookie
•
2 Posts
•
12 Points
0
0
Posted August 8th, 2026 06:00
The `TypeError: expected str, bytes or os.PathLike object, not NoneType` points more toward Ansible’s module discovery/import handling than PowerMax itself. I’d first verify the exact Ansible/Python combination and test with a clean virtual environment, then check whether the required PowerMax collection and its dependencies are installed on the execution host. Running the playbook with `-vvv` should also show which module Ansible is trying to resolve when `recursive_finder()` fails. If it works with a newer supported Ansible release, that would further indicate a compatibility issue with 2.10.2 rather than the PowerMax API.
Reply

FoolInTheRain
2 Intern
•
123 Posts
545
0
Posted October 19th, 2020 12:00
From the "Ansible Modules for Dell EMC PowerMax (1.1) Product Guide", it appears that the latest Python version supported is 3.5.2.
Have you tried Python version 3.5.2 instead of 3.8?