Community.windows compatibility issue with Ansible 2.15 in AWX causing failure in `unix_computers_in_ad` role

Get Help
, , , , ,
1

Title

community.windows compatibility issue with Ansible 2.15 in AWX causing failure in unix_computers_in_ad role

Description

I am running the unix_computers_in_ad role from the oneidentity.authentication_services collection in AWX, and encountering a failure that appears related to community.windows compatibility with my Ansible version.

The playbook targets Ubuntu (Linux) hosts and is expected to query Active Directory and generate a report.

The report is generated successfully, but the role fails during execution with the following generic error:

The module failed to execute correctly, you probably need to set the interpreter.
See stdout/stderr for the exact error

Environment

  • AWX: running on Kubernetes (k3s)
  • Ansible Core: 2.15.13
  • Python: 3.9
  • Execution: AWX Execution Environment (containerized)
  • Target hosts: Ubuntu Linux
  • AD environment: Windows Domain Controller available

Collections (requirements.yml)

---
collections:
  - name: oneidentity.authentication_services
  - name: community.windows
    version: "<3.0.0"
  - name: microsoft.ad

Note: I pinned community.windows to <3.0.0 because newer versions require Ansible >= 2.16.

Playbook

---
- hosts: all
  gather_facts: false

  vars:
    unix_computers_in_ad_facts_generate: true
    unix_computers_in_ad_reports_generate: true
    unix_computers_in_ad_reports_backup: true

    unix_computers_in_ad_reports_host: report-host

    unix_computers_in_ad_reports:
      - src: unix_computers_in_ad_report.csv.j2
        dest: /home/reports/unix_computers_in_ad_report.csv
      - src: unix_computers_in_ad_report.html.j2
        dest: /home/reports/unix_computers_in_ad_report.html

  roles:
    - oneidentity.authentication_services.unix_computers_in_ad

Output

TASK [oneidentity.authentication_services.unix_computers_in_ad : fail] *********
fatal: [UB-Host-1]: FAILED! => {"msg": "The module failed to execute correctly, you probably need to set the interpreter."}
fatal: [UB-Host-2]: FAILED! => {"msg": "The module failed to execute correctly, you probably need to set the interpreter."}

However, the report generation step still succeeds:

ok: [UB-Host-1 -> <report host>]

Observations

  • Reports are generated but appear empty or incomplete.
  • The role previously relied on community.windows.win_domain_object_info, which is deprecated/removed in newer versions.

Questions

  1. Is this issue caused by community.windows compatibility with Ansible 2.15 in AWX?
  2. What is the recommended approach for using this role with newer community.windows or microsoft.ad collections?

Additional Info

  • vastool is installed and working on target hosts.
  • AD connectivity is functional.
  • Similar roles (e.g., local_unix_users) work correctly in the same environment.

Any guidance or clarification would be appreciated :folded_hands: