Open chofstede opened 1 year ago
@sean-m-sullivan any ideas?
@sean-m-sullivan just got this error too.
I think it's because here you used ee_registry_username
: https://github.com/redhat-cop/ee_utilities/blob/devel/roles/ee_builder/tasks/00_build_ee.yml#L62-L63
And here you used ee_base_registry_username
: https://github.com/redhat-cop/ee_utilities/blob/devel/roles/ee_builder/tasks/00_build_ee.yml#L13-L14
As noted here: https://github.com/redhat-cop/ee_utilities/issues/133 there is different credentials for the base image and the destination registry.
Do you see a way to make it work for every use case?
I think it would be best to move those 4 variables inside the image definition.
This way, when using this role from aap_configuratioin_template, we can have a list of images in ee_list
with different settings for each, instead of having everything in the global scope.
EDIT: Remove mention to builder image repository. I got confused with the term "builder image" and "upstream" vs "downstream". I just start to understand what it means.
Summary
The variables ee_base_registry_username and ee_base_registry_password are not being used to authenticate to registry.redhat.io. Even when they are set to valid Red Hat Registry credentials, I still get the error: "unable to retrieve auth token: invalid username/password if the user is not logged in yet."
I added this as a workaround and it works:
Issue Type
Ansible, Collection, Docker/Podman details
Ansible installed from RPM
OS / ENVIRONMENT
RHEL9
Desired Behavior
ansible-builder should authenticate to registry.redhat.io
Actual Behavior
ansible-builder fails with "unable to retrieve auth token: invalid username/password if the user is not logged in yet."
STEPS TO REPRODUCE