You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use the collection with the destination address ee_registry_dest: controller01.localnet.local:8444/lagomes pointing to an internal Automation Hub, the collection publishes the image, but in the Automation Hub only the destination username, in this case lagomes, is displayed, ignoring the image that was uploaded.
When I forced the image name in the push_args.dest variable, it worked correctly. However, during testing, there was an issue when publishing to quay.io. In other words, I don't have problems publishing to quay.io, only when trying to publish to the private HUB.
Summary
When I use the collection with the destination address ee_registry_dest: controller01.localnet.local:8444/lagomes pointing to an internal Automation Hub, the collection publishes the image, but in the Automation Hub only the destination username, in this case lagomes, is displayed, ignoring the image that was uploaded.
Issue Type
Ansible, Collection, Controller details
.ansible/collections/ansible_collections/infra/ee_utilities/roles/ee_builder/tasks/00_build_ee.yml
When I forced the image name in the push_args.dest variable, it worked correctly. However, during testing, there was an issue when publishing to quay.io. In other words, I don't have problems publishing to quay.io, only when trying to publish to the private HUB.
The text was updated successfully, but these errors were encountered: