Closed benblasco closed 9 months ago
The desired outcome for the above can either:
sorry I forgot to reply to this, couldn't you just put the port at the end of the ee_registry_dest var?
This is the answer I've tested, the dest var, and things like ah_host can contain port variables.
Hi folks, apologis for not responding much much sooner. I ended up setting the variable as follows:
ah_host: "{{ ah_hostname | default(groups['automationhub'][0]) }}:444"
ee_registry_dest: "{{ ah_host }}"
I can't remember why I set it at the ah_host level, but I believe it was to cover off the port number being relevant in contexts beyond just hub as a container registry.
Summary
The
ee_builder
role does not have a variable where one can separately define the port used for theee_registry
. This may be required in scenarios such as the container based install, which uses port 81/444 instead of 443 for automation hub. See README for the containerised installer here: https://gitlab.cee.redhat.com/ansible/aap-containerized-installer/-/tree/mainThere is a variable defined called
ee_registry_dest
that is used byinfra.ee_utilities.ee_builder
.This is typically defined as a hostname or a reference back to the AAP inventory, e.g.
Is it valid to override the variable with something like the following?
Issue Type
Ansible, Collection, Docker/Podman details
OS / ENVIRONMENT
Ansible installed on Fedora 38 host, automating against RHEL 9.2
Desired Behavior
It would be good to have a separate variable for the registry port in case adding a port number to the
ee_registry_dest
variable has other unforeseen impacts.Actual Behavior
Please give some details of what is actually happening. Include a minimum complete verifiable example with:
STEPS TO REPRODUCE
Run through this exercise on a containerised AAP install:
https://aap2.demoredhat.com/exercises/ansible_config_as_code/1-ee/
Error message when the registry TCP port is not defined (truncated for brevity)