# AAP 2.5 Collection Issues

**URL:** <https://forum.ansible.com/t/aap-2-5-collection-issues/10856>\
**Category:** Get Help\
**Tags:** aap, galaxy-ng\
**Created:** [November 12, 2024, 5:05pm UTC](https://forum.ansible.com/t/aap-2-5-collection-issues/10856 "2024-11-12T17:05:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Strung6013](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Strung6013](https://forum.ansible.com/u/Strung6013)\
**Post date:** [November 12, 2024, 5:05pm UTC](https://forum.ansible.com/t/aap-2-5-collection-issues/10856/1 "2024-11-12T17:05:56Z")

</div>

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\n[https://localhost:8443/pulp\_ansible/galaxy/published/](https://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](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](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/](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](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](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/](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.

---

<div class="post-metadata">

**Author:** ![selvigp](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/selvigp/32/4977_2.png) [@selvigp](https://forum.ansible.com/u/selvigp)\
**Post date:** [January 17, 2025, 10:50am UTC](https://forum.ansible.com/t/aap-2-5-collection-issues/10856/2 "2025-01-17T10:50:36Z")

</div>

Hi,

Are you able to resolve above issues?

---

<div class="post-metadata">

**Author:** ![Strung6013](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Strung6013](https://forum.ansible.com/u/Strung6013)\
**Post date:** [January 17, 2025, 4:54pm UTC](https://forum.ansible.com/t/aap-2-5-collection-issues/10856/3 "2025-01-17T16:54:17Z")

</div>

Yes, I was finally able to publish all of the collections that I was trying to. Wasn’t completely straightforward as I recall, but I can do it now.

---

<div class="post-metadata">

**Author:** ![selvigp](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/selvigp/32/4977_2.png) [@selvigp](https://forum.ansible.com/u/selvigp)\
**Post date:** [January 17, 2025, 6:02pm UTC](https://forum.ansible.com/t/aap-2-5-collection-issues/10856/4 "2025-01-17T18:02:34Z")

</div>

Hi, I am trying to upload the Hashicorp vault collection into Automation Hub. But somehow it is not uploading; instead, no error. It doesn’t send uploaded collections for approval; rather, it is available in namespaces → Imports options. Could you help me on this?

I am using AAP 2.5, downloaded hashicorp vault version 6.2.0

---

<div class="post-metadata">

**Author:** ![Strung6013](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Strung6013](https://forum.ansible.com/u/Strung6013)\
**Post date:** [February 3, 2025, 6:02pm UTC](https://forum.ansible.com/t/aap-2-5-collection-issues/10856/5 "2025-02-03T18:02:35Z")

</div>

Sure I can help you push things to the PAH if you’re still needing this. I missed the reply here as it got lost in my email if you’re still needing help.

---

<div class="post-metadata">

**Author:** ![selvigp](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/selvigp/32/4977_2.png) [@selvigp](https://forum.ansible.com/u/selvigp)\
**Post date:** [February 3, 2025, 6:34pm UTC](https://forum.ansible.com/t/aap-2-5-collection-issues/10856/6 "2025-02-03T18:34:41Z")

</div>

Hi,

Thanks for getting back to me. Now, I resolved this issue.

/Selvi