While working on the issue with customer it turned out:

• they have awx, nginx, receptor etc users created on LDAP (that organization has internal policy to have all users in LDAP)
• as a result, the installer is failing for this reason: for LDAP-provided users and groups being a problem was that the systemd-tmpfiles-setup.service unit starts before sssd during system bootup. As a result, systemd-tmpfiles-setup fails to resolve the nginx group that should own the /var/run/tower directory. So the system boots up without creating /var/run/tower and some of the most important AAP services fail to start up as a result, namely the uwsgi and daphne services managed by supervisord

Customer requested if installer can have additional logic to be able to handle such scenario. At the same time docs clearly state the users need to be local users. Submitting the RFE to get Engineering/BU feedback.

Regards, Olek