# OS builds failing: Skipping Galaxy server https://galaxy.ansible.com/api/ **URL:** \ **Category:** Get Help\ **Tags:** community, galaxy-ng\ **Created:** [October 4, 2023, 5:46pm UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408 "2023-10-04T17:46:12Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![venky](https://avatars.discourse-cdn.com/v4/letter/v/c89c15/32.png) [@venky](https://forum.ansible.com/u/venky)\ **Post date:** [October 4, 2023, 5:46pm UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/1 "2023-10-04T17:46:12Z")
Getting below error message for our builds: Process install dependency map **18:33:24** /usr/local/lib/python3.6/site-packages/ansible/parsing/vault/ **init**.py:44: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography and will be removed in a future release. **18:33:26** from cryptography.exceptions import InvalidSignature **18:33:26** [WARNING]: Skipping Galaxy server [https://galaxy.ansible.com/api/](https://galaxy.ansible.com/api/). Got an **18:33:26** unexpected error when getting available versions of collection **18:33:26** community.vmware: '/api/v3/plugin/ansible/content/published/collections/index/c **18:33:26** ommunity/vmware/versions/’ **18:33:26** ERROR! Unexpected Exception, this is probably a bug: ‘/api/v3/plugin/ansible/content/published/collections/index/community/vmware/versions/’ **18:33:26** to see the full traceback, use -vvv **18:33:26** Build step ‘Execute shell’ marked build as failure **18:33:26** Finished: FAILURE We are giving the shell command thru jenkins for the community vmware installation. Below the shell command, we have added in jenkins: **ansible-galaxy collection install community.vmware** **ansible-playbook …/vm-hardware-change.yml …/export-as-ovf.yml** ---
**Author:** ![venky](https://avatars.discourse-cdn.com/v4/letter/v/c89c15/32.png) [@venky](https://forum.ansible.com/u/venky)\ **Post date:** [October 4, 2023, 6:44pm UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/2 "2023-10-04T18:44:18Z")
@rochacbruno could you please help me on this issue ---
**Author:** ![rochacbruno](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rochacbruno/32/131_2.png) [@rochacbruno](https://forum.ansible.com/u/rochacbruno)\ **Post date:** [October 4, 2023, 7:12pm UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/3 "2023-10-04T19:12:56Z")
Hi @venky thanks for reporting, this issue is already covered on [Skipping Galaxy server https://galaxy.ansible.com/api/](http://forum.ansible.com/t/skipping-galaxy-server-https-galaxy-ansible-com-api/1281) You need to be using ansible-core \>=2.13.9 to be able to download content from the new galaxy, The [https://old-galaxy.ansible.com](https://old-galaxy.ansible.com) is still available for users who need to point to that server until able to upgrade. ---
**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\ **Post date:** [October 4, 2023, 7:31pm UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/4 "2023-10-04T19:31:56Z")
I’m glad you got an answer, but for the record, please try not ping individuals unless you _really_ need them - that just causes stress. The person may be busy, on holiday, or otherwise unavailable. The Galaxy team are hard at work on all of the #galaxy-ng tagged topics, and we can group-ping the Galaxy team when issues might have slipped past the triage - but that’s after a matter of days, not hours. Thanks for understanding! ---
**Author:** ![veritasium](https://avatars.discourse-cdn.com/v4/letter/v/87869e/32.png) [@veritasium](https://forum.ansible.com/u/veritasium)\ **Post date:** [October 4, 2023, 7:51pm UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/5 "2023-10-04T19:51:39Z")
I think the latest AWX is running ansible-core 2.15.x and the issue is still there. ---
**Author:** ![venky](https://avatars.discourse-cdn.com/v4/letter/v/c89c15/32.png) [@venky](https://forum.ansible.com/u/venky)\ **Post date:** [October 5, 2023, 5:21am UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/6 "2023-10-05T05:21:34Z")
Hi @rochacbruno, Thanks for your reply. I just have a doubt, if we want to point to old galaxy, what changes need to be added in the command. for example, I’m currently using the command **ansible-galaxy collection install community.vmware** what could be the new command for using the old galaxy. Regards, Venky ---
**Author:** ![venky](https://avatars.discourse-cdn.com/v4/letter/v/c89c15/32.png) [@venky](https://forum.ansible.com/u/venky)\ **Post date:** [October 5, 2023, 7:13am UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/7 "2023-10-05T07:13:49Z")
Hi team, Thanks noted. I just have a doubt, if we want to point to old galaxy, what changes need to be added in the command. for example, I’m currently using the command **ansible-galaxy collection install community.vmware** what could be the new command for using the old galaxy. Kindly help me on this also. Thanks, Venky ---
**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\ **Post date:** [October 5, 2023, 9:56am UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/8 "2023-10-05T09:56:24Z")
[Skipping Galaxy server https://galaxy.ansible.com/api/ - #6 by aberkvam\_twh](http://forum.ansible.com/t/skipping-galaxy-server-https-galaxy-ansible-com-api/1281/6) would appear to be what you need. ---
**Author:** ![venky](https://avatars.discourse-cdn.com/v4/letter/v/c89c15/32.png) [@venky](https://forum.ansible.com/u/venky)\ **Post date:** [October 5, 2023, 10:06am UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/9 "2023-10-05T10:06:13Z")
Hello, Server link is fine. We are install the community galaxy thru command " **ansible-galaxy collection install community.vmware** Is there any command that we can use it for alternate? Thanks, Venky ---
**Author:** ![venky](https://avatars.discourse-cdn.com/v4/letter/v/c89c15/32.png) [@venky](https://forum.ansible.com/u/venky)\ **Post date:** [October 10, 2023, 5:23am UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/10 "2023-10-10T05:23:11Z")
Hello @rochacbruno Server link is fine. We are install the community galaxy thru command " **ansible-galaxy collection install community.vmware** Is there any command that we can use it for alternate? Thanks, Venky ---
**Author:** ![shertel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shertel/32/1241_2.png) [@shertel](https://forum.ansible.com/u/shertel)\ **Post date:** [October 10, 2023, 2:04pm UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/11 "2023-10-10T14:04:37Z")
In addition to the solutions suggested already, you can pass a preferred server to try first: ansible-galaxy collection install community.vmware --server [https://old-galaxy.ansible.com](https://old-galaxy.ansible.com) Or to configure only the old server via the CLI: ANSIBLE\_GALAXY\_SERVER\_LIST= ANSIBLE\_GALAXY\_SERVER=[https://old-galaxy.ansible.com](https://old-galaxy.ansible.com) ansible-galaxy collection install community.vmware Another way to do that: ANSIBLE\_GALAXY\_SERVER\_LIST=legacy\_server ANSIBLE\_GALAXY\_SERVER\_LEGACY\_SERVER\_URL=[https://old-galaxy.ansible.com](https://old-galaxy.ansible.com) ansible-galaxy collection install community.vmware ---
**Author:** ![briantist](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/briantist/32/130_2.png) [@briantist](https://forum.ansible.com/u/briantist)\ **Post date:** [October 15, 2023, 10:26pm UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/12 "2023-10-15T22:26:39Z")
> You need to be using ansible-core \>=2.13.9 to be able to download content from the new galaxy, Anecdotally, galaxy v3 support is available even in Ansible 2.9, and from what I could tell it works fine with the new galaxy. I know there was a bug in 2.13.x(?) (don’t know which patch versions were affected) but I don’t think that bug affected 2.12 or earlier versions. It would be nice to clarify this requirement. ---
**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\ **Post date:** [November 14, 2023, 10:26pm UTC](https://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/13 "2023-11-14T22:26:40Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.