AAP 2.5 Installation with gateway URL different from hostname

Hi all,
I’m stuck in the installation process for AAP 2.5.
I’d like to use a URL for the gateway which is different from the hostname.
FQDN: test.corp.name.com
URL: aap.newname.de

There are custom certificates defined for the URL

I am using the URL as hostname in the inventory.

Now I get the following error:

TASK [ansible.containerized_installer.automationgateway : Update automation platform gateway service clusters] ***************************************************************
task path: /home/ansible/install_aap2513/collections/ansible_collections/ansible/containerized_installer/roles/automationgateway/tasks/postinstall.yml:35
failed: [aap.newname.de] (item={'name': 'gateway', 'service_type': 'gateway'}) => {"ansible_loop_var": "item", "changed": false, "item": {"name": "gateway", "service_type": "gateway"}, "msg": "c{'service_type': ['Incorrect type. Expected pk value, received str.']}"}
failed: [aap.newname.de] (item={'name': 'controller', 'service_type': 'controller'}) => {"ansible_loop_var": "item", "changed": false, "item": {"name": "controller", "service_type": "controller"}, "msg": "c{'service_type': ['Incorrect type. Expected pk value, received str.']}"}
failed: [aap.newname.de] (item={'name': 'hub', 'service_type': 'hub'}) => {"ansible_loop_var": "item", "changed": false, "item": {"name": "hub", "service_type": "hub"}, "msg": "c{'service_type': ['Incorrect type. Expected pk value, received str.']}"}
failed: [aap.newname.de] (item={'name': 'eda', 'service_type': 'eda'}) => {"ansible_loop_var": "item", "changed": false, "item": {"name": "eda", "service_type": "eda"}, "msg": "c{'service_type': ['Incorrect type. Expected pk value, received str.']}"}

I had an issue with a task regarding the certification verification when the gateway starts during the process. But could solve it by adding the custom ca certs (root and intermediate) to the trust store which is located in the aap directory aap/tls/extracted/pem/tls-ca-bundle.pem.

Don’t know if the earlier issue has an impact, but think it might be important, that I did a manual change inside the aap installation.

Hope someone can help?

Best regards,
Rainer

Ok, some updates from my side.

The solution I found to overcome the failing certification check when the automation-gateway ist started, is not lasting.
The installation seems to fail to add the custom certifications to the locally used pki trust files in aap/tls/… or ~/.local/share/…

I also tried to use release 2.5.15 instead of 2.5.13, no change.

Still open for any suggestions and questions.

Cheers,
Rainer