# Redhat.rhel\_system\_roles

**URL:** <https://forum.ansible.com/t/redhat-rhel-system-roles/46289>\
**Category:** Get Help\
**Tags:** windows, rhel, fedora, aap, ansible, ee\
**Created:** [September 9, 2026, 6:33pm UTC](https://forum.ansible.com/t/redhat-rhel-system-roles/46289 "2026-09-09T18:33:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fracture7144](https://avatars.discourse-cdn.com/v4/letter/f/73ab20/32.png) [@Fracture7144](https://forum.ansible.com/u/Fracture7144)\
**Post date:** [September 9, 2026, 6:33pm UTC](https://forum.ansible.com/t/redhat-rhel-system-roles/46289/1 "2026-09-09T18:33:59Z")

</div>

Is anyone importing and or using the redhat.rhel\_system\_roles.ad\_integration or fedora.linux\_system\_roles.ad\_integration ?

I am trying to use this to automate our linux servers to authenticate to Active Directory (wasn’t my choice). I would say that 80% of my servers are RHEL 8 and the rest are RHEL 9 or something earlier that RHEL 8. I’m focusing on RHEL =\>8. I THINK it might be related with my EE which is built on RHEL 8 using python 3.11 but also has python 3.9 installed to account for RHEL 8. So when I go to run the role in AAP, it ALWAYS fails at the following:

`TASK [fedora.linux_system_roles.ad_integration : Build Command - Join to a specific Domain Controller] ***`

`task path: /runner/requirements_collections/ansible_collections/fedora/linux_system_roles/roles/ad_integration/tasks/main.yml:193`

`fatal: [$HOSTNAME]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}`

---

<div class="post-metadata">

**Author:** ![clasp\_acting733](https://avatars.discourse-cdn.com/v4/letter/c/a3d4f5/32.png) [@clasp\_acting733](https://forum.ansible.com/u/clasp_acting733)\
**Post date:** [September 14, 2026, 6:06pm UTC](https://forum.ansible.com/t/redhat-rhel-system-roles/46289/2 "2026-09-14T18:06:07Z")

</div>

We use the fedora.linux\_system\_roles.ad\_integration flavor, and it works. Without knowing more about your environment or deeper context into what you’ve already tried, here is what I’d recommend.

1. Check which version of ansible-core is actually declared/installed in your EE; v2.16 is the last to support RHEL 8, IIRC. Since your EE is built on RHEL 8, you’re probably fine, but it’s worth verifying. We build our EE on CentOS 10, but limit the ansible-core version to \<2.17 for that reason.

2. The ad\_integration role has a default variable to keep logging secure. Take the appropriate measures (password rotation after, run the role locally without external logging, etc), and temporarily disable the secure logging flag. That will get you some more context as to why that task is failing. [ad\_integration/tasks/main.yml at 72fa163f24f24caf42a1b03cb6cd7e40ef479450 · linux-system-roles/ad\_integration · GitHub](https://github.com/linux-system-roles/ad_integration/blob/72fa163f24f24caf42a1b03cb6cd7e40ef479450/tasks/main.yml#L215)

For reference, here are the only vars we are overriding and setting in our environment to make it functional. Some of these are optional, but maybe one is required and you missed it. The password is vaulted, so we also pass the vault credential in AWX at the same time.

ad\_integration\_realm  
ad\_integration\_user  
ad\_integration\_password  
ad\_integration\_auto\_id\_mapping  
ad\_integration\_computer\_ou  
ad\_integration\_sssd\_settings  
ad\_integration\_sssd\_custom\_settings