How to skip pwsh component from sanity test

prabhuk · February 24, 2026, 7:13am

Hello Community!
I need some help to skip/exclude the ‘pwsh’ component from integration tests.
I was building ansible package and executing Unit, Sanity and Integration tests on ppc64le arch, but in Integration tests few tests requires pwsh (powershell) components, but it was not supported on ppc64le, so wont’ be able to install.
I tried to skip that component by using flag ANSIBLE_SKIP_PWSH_MODULES=1 but didn’t work. Also didn’t found anything related to skip that properly.
Could you please help me what to do in this situation?
Below are the error logs for your reference:

Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 23.2.1
    Not uninstalling pip at /usr/lib/python3.12/site-packages, outside environment /tmp/tmp.tgg653nqP2/ansible_collections/ns/col/sts/output/.tmp/delegation/python3.12-ssp
    Can't uninstall 'pip'. No files were found to uninstall.
Successfully installed pip-25.2
Running sanity test "action-plugin-docs"
Running sanity test "ansible-doc"
Running sanity test "changelog"
Running sanity test "compile" on Python 3.12
Running sanity test "empty-init"
Running sanity test "ignores"
Running sanity test "import" on Python 3.12
Running sanity test "line-endings"
Running sanity test "no-assert"
Running sanity test "no-get-exception"
Running sanity test "no-illegal-filenames"
Running sanity test "no-smart-quotes"
Running sanity test "pep8"
Running sanity test "pslint"
WARNING: Required program "pwsh" not found.
Running sanity test "pylint"
Running sanity test "replace-urlopen"
Running sanity test "runtime-metadata"
Running sanity test "shebang"
Running sanity test "shellcheck"
Running sanity test "symlinks"
Running sanity test "use-argspec-type-path"
Running sanity test "use-compat-six"
Running sanity test "validate-modules"
FATAL: Command "/root/.ansible/test/venv/sanity.validate-modules/3.12/8088ee77/bin/python /root/a/ansible/test/lib/ansible_test/_ul/controller/sanity/validate-modules/validate.py --format json --arg-spec --collection ansible_collections/ns/col --collection-veron 1.0.0 plugins/modules/hello.py plugins/modules/win_util_args.ps1 plugins/modules/win_util_args.py" returned exit status 1.
>>> Standard Error
Traceback (most recent call last):
  File "/root/a/ansible/test/lib/ansible_test/_util/controller/sanity/validate-modules/validate.py", line 6, in <module>
    main()
  File "/root/a/ansible/test/lib/ansible_test/_util/controller/sanity/validate-modules/validate_modules/main.py", line 2692, in ma
    run()
  File "/root/a/ansible/test/lib/ansible_test/_util/controller/sanity/validate-modules/validate_modules/main.py", line 2652, in ru
    mv1.validate()
  File "/root/a/ansible/test/lib/ansible_test/_util/controller/sanity/validate-modules/validate_modules/main.py", line 2458, in vadate
    self._validate_ansible_module_call(docs)
  File "/root/a/ansible/test/lib/ansible_test/_util/controller/sanity/validate-modules/validate_modules/main.py", line 1372, in _vidate_ansible_module_call
    spec, kwargs = get_ps_argument_spec(self.path, self.collection)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/a/ansible/test/lib/ansible_test/_util/controller/sanity/validate-modules/validate_modules/module_args.py", line 104,n get_ps_argument_spec
    raise FileNotFoundError('Required program for PowerShell arg spec inspection "pwsh" not found.')
FileNotFoundError: Required program for PowerShell arg spec inspection "pwsh" not found.
FATAL: Command "/usr/bin/env ANSIBLE_TEST_CONTENT_ROOT=/tmp/tmp.tgg653nqP2/ansible_collections/ns/col PYTHONPATH=/tmp/ansible-testx7o81gn /tmp/tmp.tgg653nqP2/ansible_collections/ns/col/tests/output/.tmp/delegation/python3.12-ssp/bin/python /root/a/ansible/bin/sible-test sanity --containers '{}' --truncate 0 --color yes --host-path tests/output/.tmp/host-r3q2lej6 --metadata tests/output/.p/metadata-opcyba7g.json" returned exit status 1.
+ rm -rf /tmp/tmp.tgg653nqP2
NOTICE: To resume at this test target, use the option: --start-at ansible-test-docker
NOTICE: To resume after this test target, use the option: --start-at ansible-test-git
FATAL: Command "./runme.sh" returned exit status 1.
mv: cannot stat '.ps1_backup_temp/*.ps1': No such file or directory
Restored 1 .ps1 modules

gundalow · February 24, 2026, 10:31am

@mattclay Do you know why ANSIBLE_SKIP_PWSH_MODULES isn’t working as expected, @prabhuk is trying to skip this as it’s not available on ppc64le

jborean · February 24, 2026, 12:39pm

Do you know why ANSIBLE_SKIP_PWSH_MODULES isn’t working as expected

I’ve not heard or seen any reference to this environment variable or any like that. Is it documented anywhere?

prabhuk · February 24, 2026, 2:37pm

No, it was not documented anywhere, I have used it while executing build script and tried to skip, but still pwsh components were executing.
Could you please provide more info how pwsh component invoke and how we can exclude?

gundalow · February 24, 2026, 3:57pm

@prabhuk I don’t see any reference to SKIP_PWSH_MODULES in the Ansible codebase, though maybe I’m looking in the wrong place.
Where did you find reference to it?

prabhuk · February 24, 2026, 5:01pm

Yeah, as I mentioned earlier I was executing integration test and it was calling inside it, mentioned few reference which i found, it might not be exact ones, since I can see pwsh is calling from many places,

github.com/ansible/ansible

test/lib/ansible_test/_util/controller/sanity/validate-modules/validate_modules/module_args.py

a751010be


      
                  for k in list(sys.modules.keys()):
                      # It's faster if we limit to items in ansible.module_utils
                      # But if this causes problems later, we should remove it
                      if k not in pre_sys_modules and k.startswith('ansible.module_utils.'):
                          del sys.modules[k]
          
          
          def get_ps_argument_spec(filename, collection):
              fqc_name = get_module_name_from_filename(filename, collection)
          
              pwsh = find_executable('pwsh')
              if not pwsh:
                  raise FileNotFoundError('Required program for PowerShell arg spec inspection "pwsh" not found.')
          
              module_path = os.path.join(os.getcwd(), filename)
              b_module_path = to_bytes(module_path, errors='surrogate_or_strict')
              with open(b_module_path, mode='rb') as module_fd:
                  b_module_data = module_fd.read()
          
              ps_dep_finder = PSModuleDepFinder()
              module_deps = ps_dep_finder.scan_module(b_module_data, fqn=fqc_name)

ansible/test/integration/targets/ansible-test-sanity-validate-modules/runme.sh at a751010beaeeeeda97fd688e609f6035e9698ad2 · ansible/ansible

Akasurde · February 24, 2026, 5:10pm

What is the command you are trying? Is there any PowerShell modules in your source directory?

mattclay · February 24, 2026, 5:54pm

There is no ANSIBLE_SKIP_PWSH_MODULES environment variable or setting.

Not all integration tests will work on ppc64le. For those cases, you’ll need to skip those tests. Tests that rely on PowerShell are one example of this, but there are others.

prabhuk · February 25, 2026, 12:15am

Yeah, there are many PowerShell dependent modules in ansible, currently getting an error from - plugins/modules/win_util_args.ps1
I was executing an Integration test with command “./bin/ansible-test integration --python 3.12” which internally triggers sanity test “ansible-test sanity --test validate-modules”

prabhuk · February 25, 2026, 12:22am

oh, ok, Can I know how if there are any other way apart from –exclude to skip those tests?
And by any chance list of tests which are not supported on ppc64le, it saves me a lot of time.

mattclay · February 25, 2026, 12:49am

Using --exclude is the correct way to skip integration tests that would otherwise match the test criteria you specified. Keep in mind the argument is a regular expression, so you can specify multiple test targets at once, such as --exclude 'some_test|another_test'

We do not maintain a list of tests which are unsupported on specific architectures, since doing so is impractical.

Akasurde · February 25, 2026, 12:53am

We don’t have ppc64le hardware, so we can’t tell you right away which tests would fail.

You can use aliases to disable test which does not work for ppc64le hardware. Please refer integration-aliases — Ansible Community Documentation for more details.

Thanks,

prabhuk · March 16, 2026, 11:22am

Hello Team,

I have completed the integration tests after excluding the cases that fail on ppc64le due to unsupported dependencies. The following 13 test cases are currently being excluded because they are failing:

--exclude ansible-test-cloud-galaxy
--exclude ansible-galaxy-collection
--exclude ansible-test-coverage
--exclude ansible-test-docker
--exclude connection_ssh
--exclude fetch
--exclude file
--exclude keyword_inheritance
--exclude lookup_password
--exclude omit
--exclude async
--exclude callback_default
--exclude remote_tmp

Could you please confirm if it is fine to exclude this many test cases for ppc64le while verifying the integration tests?

Akasurde · March 16, 2026, 11:41am

Could you please create a separate repo for logs for each failure so that we can take a look and let you know? Thanks,

Topic		Replies	Views
ERROR: invalid-extension: Official Ansible modules must have Project Discussions ansible-test	4	378	May 13, 2024
Skip the errors during sanity testing in ansible 3.x version Get Help collections , documentation	1	52	October 17, 2024
How to tell win_powershell module which version of PowerShell to use Get Help collections , windows , powershell	3	1188	February 15, 2024
ANSIBALLZ_WRAPPER is not recognized as the name \r\nof a cmdlet Ansible Developer ubuntu , windows	5	64	February 28, 2018
Using powershell module in task: "no action detected" Ansible Developer windows	7	41	January 14, 2016

How to skip pwsh component from sanity test

Related topics