@Hugo B 

I've managed to get AAP running on Rocky Linux 9.2 by making the following changes.

SETUP.SH

    if [ -z "${RETVAL}" ]; then
        RETVAL="unknown"
    fi

##
## "Force" RETVAL to be RedHat even though actually Rocky Linux 9.2
##
	RETVAL="rhel"

    echo ${RETVAL}
}

INSTALL.YML

Within the "Group nodes by OS distribution" I added a set_facts

- name: "Group nodes by OS distribution"
  hosts: aap_valid_hosts
  gather_facts: false
  tasks:
    - name: "*** SET FACTS ***"
      set_fact:
        ansible_distribution: "RedHat"
        ansible_distribution_major_version: "9" 
        ansible_distribution_version: "9.2"
        
    - name: group hosts by distribution
      group_by:
        key: "{{ ansible_distribution }}_{{ ansible_distribution_major_version }}"
      changed_when: false

- name: "Group supported distributions"
  hosts: RedHat_8:RedHat_9
  gather_facts: false
  tasks:
    - name: group hosts for supported distributions
      group_by: key="supported"
      changed_when: false
      when: ansible_distribution_version is version_compare('8.6', '>=')

I then ran the install.sh script

PLAY RECAP *********************************************************************
xxxxxxxxx                 : ok=370  changed=164  unreachable=0    failed=0    skipped=233  rescued=0    ignored=7
localhost                  : ok=0    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0

The setup process completed successfully.
Setup log saved to /var/log/tower/setup-2023-07-06-07:39:14.log.

I pointed my browser to AAP, logged on and then followed the Wizard to select the 60-day trial subscription.

So far so good!

Steve

@Hugo B 

I'm presuming it's not "just" a case of commenting out this piece before running?

- name: "Ensure all node OS distributions are supported"
  hosts: aap_valid_hosts:!supported
  gather_facts: false
  tasks:
    - name: fail for unsupported distribution
      fail: msg="{{ ansible_distribution }} {{ ansible_distribution_version }}
                 is not a supported OS for an Ansible Automation Platform installation.
                 Supported OSes include Red Hat Enterprise Linux 8.6+."

As I presume the script needs to think it's (really) working with RHEL v9.  Would updating "just" the setup.sh script to "hard wire" things work I wonder?

I'll await your thoughts/blog :-)

Many thanks, Steve

In general by removing in the scritps the lines where RHEL says that a RHEL "clone" is not supported :) ... which is true, but it should also work which is our purpose. If I have time I will write a blog about my adventures with Rocky, Alma and OpenSUSE on ppc64le. I think they are great allies for Linux projects on Power. In this case I used RHEL where ALMA/Rocky where the clients. I will try the other way and let u know how it works!

@Hugo B 

How did you get AAP working on Rocky Linux as I'm getting the following when running the setup.sh script.

"msg": "Rocky 9.2 is not a supported OS for an Ansible Automation Platform installation. Supported OSes include Red Hat Enterprise Linux 8.6+."

Many thanks, Steve

Up and running, deploying both Rocky and Alma Linux on pp64le smoothly. Great work team!

Great news. Installed it last night on our IBM Power environment, simple process and it works well.

Long asked for, now it's there: Ansible Automation Platform on IBM Power. 
No need for x86 , polluting pure-bred IBM Power landscapes.  This shows: IBM is walking the talk.....

Elevating IBM Power from simple  "Endpoint" to "Controller" establishes "first-row seating" in IT Landscapes !

Big Thank You to all the involved developers.