I think that I have made some progress on installing AAP 2.5 in the containerized manner. My issue is around publishing my own collection to my PAH. If I try to publish it via the GUI then it imports as expected, but when I try to run a job that uses the custom module, I get the following error.
{
“changed”: true,
“stdout”: “Starting galaxy collection install process\nProcess install dependency map”,
“stderr”: “[DEPRECATION WARNING]: ANSIBLE_COLLECTIONS_PATHS option, does not fit var \nnaming standard, use the singular form ANSIBLE_COLLECTIONS_PATH instead. This \nfeature will be removed from ansible-core in version 2.19. Deprecation warnings\n can be disabled by setting deprecation_warnings=False in ansible.cfg.\n[WARNING]: Skipping Galaxy server\nhttps://localhost:8443/pulp_ansible/galaxy/published/. Got an unexpected error\nwhen getting available versions of collection test_collection.titan: Unknown\nerror when attempting to call Galaxy at\n’https://localhost:8443/pulp_ansible/galaxy/published/api’: <urlopen error\n[Errno 111] Connection refused>. <urlopen error [Errno 111] Connection refused>\nERROR! Unknown error when attempting to call Galaxy at ‘https://localhost:8443/pulp_ansible/galaxy/published/api’: <urlopen error [Errno 111] Connection refused>. <urlopen error [Errno 111] Connection refused>”,
“rc”: 1,
“cmd”: [
“ansible-galaxy”,
“collection”,
“install”,
“-r”,
“/home/REMOVED/aap/controller/data/projects/_8__bitbucket/collections/requirements.yml”
],
“start”: “2024-11-12 15:27:00.132202”,
“end”: “2024-11-12 15:27:00.744673”,
“delta”: “0:00:00.612471”,
“msg”: “non-zero return code”,
“invocation”: {
“module_args”: {
“chdir”: “/home/REMOVED/aap/controller/data/projects/_8__bitbucket”,
“_raw_params”: "ansible-galaxy collection install -r /home/REMOVED/aap/controller/data/projects/_8__bitbucket/collections/requirements.yml ",
“_uses_shell”: false,
“expand_argument_vars”: true,
“stdin_add_newline”: true,
“strip_empty_ends”: true,
“argv”: null,
“executable”: null,
“creates”: null,
“removes”: null,
“stdin”: null
}
},
“stdout_lines”: [
“Starting galaxy collection install process”,
“Process install dependency map”
],
“stderr_lines”: [
"[DEPRECATION WARNING]: ANSIBLE_COLLECTIONS_PATHS option, does not fit var ",
"naming standard, use the singular form ANSIBLE_COLLECTIONS_PATH instead. This “,
“feature will be removed from ansible-core in version 2.19. Deprecation warnings”,
" can be disabled by setting deprecation_warnings=False in ansible.cfg.”,
“[WARNING]: Skipping Galaxy server”,
“https://localhost:8443/pulp_ansible/galaxy/published/. Got an unexpected error”,
“when getting available versions of collection test_collection.titan: Unknown”,
“error when attempting to call Galaxy at”,
“‘https://localhost:8443/pulp_ansible/galaxy/published/api’: <urlopen error”,
“[Errno 111] Connection refused>. <urlopen error [Errno 111] Connection refused>”,
“ERROR! Unknown error when attempting to call Galaxy at ‘https://localhost:8443/pulp_ansible/galaxy/published/api’: <urlopen error [Errno 111] Connection refused>. <urlopen error [Errno 111] Connection refused>”
],
“_ansible_no_log”: false
}
that collection is configured with the following URL:
https://REMOVED:8443/pulp_ansible/galaxy/published/
I can see that the collection is listed in the PAH namespace.collection and is approved. When I try to use it, I get the following error:
fatal: [localhost]: FAILED! => {“changed”: true, “cmd”: [“ansible-galaxy”, “collection”, “install”, “-r”, “/home/REMOVED/aap/controller/data/projects/_8__bitbucket/collections/requirements.yml”], “delta”: “0:00:00.612471”, “end”: “2024-11-12 15:27:00.744673”, “msg”: “non-zero return code”, “rc”: 1, “start”: “2024-11-12 15:27:00.132202”, “stderr”: “[DEPRECATION WARNING]: ANSIBLE_COLLECTIONS_PATHS option, does not fit var \nnaming standard, use the singular form ANSIBLE_COLLECTIONS_PATH instead. This \nfeature will be removed from ansible-core in version 2.19. Deprecation warnings\n can be disabled by setting deprecation_warnings=False in ansible.cfg.\n[WARNING]: Skipping Galaxy server\nhttps://$encrypted$:$encrypted$/pulp_ansible/galaxy/published/. Got an unexpected error\nwhen getting available versions of collection test_collection.titan: Unknown\nerror when attempting to call Galaxy at\n’https://$encrypted$:$encrypted$/pulp_ansible/galaxy/published/api’: <urlopen error\n[Errno 111] Connection refused>. <urlopen error [Errno 111] Connection refused>\nERROR! Unknown error when attempting to call Galaxy at ‘https://$encrypted$:$encrypted$/pulp_ansible/galaxy/published/api’: <urlopen error [Errno 111] Connection refused>. <urlopen error [Errno 111] Connection refused>”, “stderr_lines”: ["[DEPRECATION WARNING]: ANSIBLE_COLLECTIONS_PATHS option, does not fit var ", "naming standard, use the singular form ANSIBLE_COLLECTIONS_PATH instead. This “, “feature will be removed from ansible-core in version 2.19. Deprecation warnings”, " can be disabled by setting deprecation_warnings=False in ansible.cfg.”, “[WARNING]: Skipping Galaxy server”, “https://$encrypted$:$encrypted$/pulp_ansible/galaxy/published/. Got an unexpected error”, “when getting available versions of collection test_collection.titan: Unknown”, “error when attempting to call Galaxy at”, “‘https://$encrypted$:$encrypted$/pulp_ansible/galaxy/published/api’: <urlopen error”, “[Errno 111] Connection refused>. <urlopen error [Errno 111] Connection refused>”, “ERROR! Unknown error when attempting to call Galaxy at ‘https://$encrypted$:$encrypted$/pulp_ansible/galaxy/published/api’: <urlopen error [Errno 111] Connection refused>. <urlopen error [Errno 111] Connection refused>”], “stdout”: “Starting galaxy collection install process\nProcess install dependency map”, “stdout_lines”: [“Starting galaxy collection install process”, “Process install dependency map”]}
I’m hoping that I’m just making a simple error, but any and all help to get around this issue would be much appreciated.
Please let me know what other information I can provide to help figure this out as it’s bugging me to no end.