Switching to ansible.platform 2.6.20260306 seems to break infra.aap_configuration.gateway_role_team_assignments

[isuftin]

Summary

We've been using the latest version of infra.aap_configuration 4.3.0 without issue. We were using it with ansible.platform 2.6.20251106

When we updated to ansible.platform 2.6.20260306, it looks like this errors:

• name: Assign Roles To Teams
  ansible.builtin.include_role:
  name: infra.aap_configuration.gateway_role_team_assignments
  vars:
  gateway_role_team_assignments:
  - assignment_objects:
  - name: My Organization - Development
  type: organizations
  role_definition: "Launch User Role - Projects"
  team: Launch Development

Issue Type

• Bug Report

Ansible, Collection, Controller details

ansible --version

ansible [core 2.18.15]
  config file = /root/.ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.13/site-packages/ansible
  ansible collection location = /root/.ansible/collections/ansible_collections
  executable location = /usr/local/bin/ansible
  python version = 3.13.12 (main, Mar 19 2026, 15:29:37) [GCC 15.2.0] (/usr/local/bin/python)
  jinja version = 3.1.6
  libyaml = True

ansible-galaxy collection list

# /root/.ansible/collections/ansible_collections
Collection                               Version
---------------------------------------- ------------
ansible.controller                       4.7.10
ansible.eda                              2.11.0
ansible.hub                              1.0.6
ansible.platform                         2.6.20251106
infra.aap_configuration                  4.3.0

Controller version

Ansible Automation Platform 2.6

Automation Controller Version 4.7.9
Event-Driven Ansible Version 1.2.6
Automation Hub Version 4.11.6

• ansible installation method: pip

OS / ENVIRONMENT

Running ansible in a Docker container via Ansible 11 (also tried 13) and on MacOS with the same

Desired Behavior

No errors

Actual Behavior

Please give some details of what is actually happening.
Include a [minimum complete verifiable example] with:

• playbook / task
• configuration file / list
• error

TASK [Assign Roles To Teams] ******************************************************************************************************************************************************************************************
included: infra.aap_configuration.gateway_role_team_assignments for localhost

TASK [infra.aap_configuration.gateway_role_team_assignments : Validating arguments against arg spec 'main' - An Ansible Role to create role_team_assignments on Ansible gateway for AAP 2.6+.] ************************
ok: [localhost]

TASK [infra.aap_configuration.gateway_role_team_assignments : Role Team Assignments | Configuration] ******************************************************************************************************************
ok: [localhost] => (item=Create/Update Role Team Assignments on Gateway Launch User Role - Projects)

TASK [Role Team Assignments | Wait for finish the configuration] ******************************************************************************************************************************************************
included: infra.aap_configuration.collect_async_status for localhost => (item=Create/Update Role Team Assignments Launch User Role - Projects | Wait for finish the Role Team Assignments creation)

TASK [infra.aap_configuration.collect_async_status : Create/Update Role Team Assignments Launch User Role - Projects | Wait for finish the Role Team Assignments creation] ********************************************
[DEPRECATION WARNING]: Conditional result at location /root/.ansible/collections/ansible_collections/infra/aap_configuration/roles/collect_async_status/tasks/main.yml 9:14 was of type 'int'. Conditional results
should only be True or False. The result was interpreted as True. This feature will be removed in version 2.19. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
fatal: [localhost]: FAILED! => {"ansible_job_id": "j927499369051.419", "attempts": 1, "changed": false, "finished": 1, "msg": "{'object_id': 'Project matching query does not exist.'}", "results_file": "/root/.ansibl
e_async/j927499369051.419", "started": 1, "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}
...ignoring

TASK [infra.aap_configuration.collect_async_status : Register value] **************************************************************************************************************************************************
ok: [localhost]

TASK [infra.aap_configuration.collect_async_status : Handle Async Job Failure] ****************************************************************************************************************************************
included: /root/.ansible/collections/ansible_collections/infra/aap_configuration/roles/collect_async_status/tasks/handle_error.yml for localhost => (item=(censored due to no_log))

TASK [infra.aap_configuration.collect_async_status : handle_error | Show error and stop execution] ********************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "error: {'object_id': 'Project matching query does not exist.'}"}

TASK [infra.aap_configuration.gateway_role_team_assignments : Cleanup async results files] ****************************************************************************************************************************
ok: [localhost] => (item=Cleaning up job results file: /root/.ansible_async/j927499369051.419)

PLAY RECAP ************************************************************************************************************************************************************************************************************
localhost                  : ok=22   changed=0    unreachable=0    failed=1    skipped=1    rescued=0    ignored=1

STEPS TO REPRODUCE

- name: Assign Roles To Teams
  ansible.builtin.include_role:
    name: infra.aap_configuration.gateway_role_team_assignments
  vars:
    gateway_role_team_assignments:
      - assignment_objects:
          - name: My Organization - Development
             type: organizations
         role_definition: "Launch User Role - Projects"
         team: Launch Development    

Installing the latest ansible.platform returns the error. Installing 2.6.20251106 shows no issues.

I'd open the issue with the code base for ansible.platform but not sure how to do that.

[Pieter-Visscher]

Hi, I've been looking into assigning roles with the gateway_role_team_assignments role and have run into the same issue.
The infra.aap_configuration.gateway_role_team_assignments collection utilizes the ansible.controller.role_team_assignment role under the hood.
That has the following comment in its source code:

notes:

• This module is subject to limitations of the RBAC system in AAP 2.6.
• Global roles (e.g. Platform Auditor) cannot be assigned to teams.
• Team roles cannot be assigned to another team (Team Admin → Team is not supported).
• Organization Member role cannot be assigned to teams.
• Only resource-scoped organization roles (e.g. "Organization Inventory Admin", "Organization Credential Admin") can be meaningfully assigned to teams.
• Attempting unsupported role assignments will result in errors.
  Source

As I have multiple teams with different permissions working in the same organization, using organization roles was not an option. I've ended up solving it by doing API calls with ansible.builtin.uri to https://{{ aap_hostname }}/api/gateway/v1/role_team_assignments/

[djdanielsson]

I have looked into this a bit and I believe this is a bug in the module not in our collection. If you believe that isn't correct let me know why and provide more details.