Warning: GALAXY_COLLECTION_SIGNING_SERVICE when using Ansible Automation Hub as an operator.

Solution Verified - Updated -

Environment

  • Red Hat OpenShift Container Platform
    • 4.9+
  • Red Hat Ansible Automation Platform 2.3, 2.4

Issue

  • When running Ansible Automation Hub as an operator, the below warning pops always in Collections and Execution Environments pages:
"WARNING:GALAXY_COLLECTION_SIGNING_SERVICE is set to 'ansible-default', however the respective SigningService does not exist in the database."
"WARNING:GALAXY_CONTAINER_SIGNING_SERVICE is set to 'container-default', however the respective SigningService does not exist in the database."

Resolution

1) As a workaround , add the following lines on the Automation Hub YAML file under "spec:" section:

spec:
  pulp_settings:
    galaxy_collection_signing_service: ''
    galaxy_container_signing_service: ''

2) Restart the Automation Hub Pods.

Root Cause

  • Red Hat is aware of this issue and the issue has been raised to address this
    warning on AAP operator 2.3.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments