OS builds failing: Skipping Galaxy server https://galaxy.ansible.com/api/

Get Help
,
1

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/. 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

2

@rochacbruno could you please help me on this issue

3

Hi @venky thanks for reporting,

this issue is already covered on Skipping Galaxy server https://galaxy.ansible.com/api/

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 is still available for users who need to point to that server until able to upgrade.

1 Like
4

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!

5

I think the latest AWX is running ansible-core 2.15.x and the issue is still there.

6

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

7

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

8

Skipping Galaxy server https://galaxy.ansible.com/api/ - #6 by aberkvam_twh would appear to be what you need.

1 Like
9

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

10

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

11

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

Or to configure only the old server via the CLI:

ANSIBLE_GALAXY_SERVER_LIST= ANSIBLE_GALAXY_SERVER=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 ansible-galaxy collection install community.vmware

12

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.

13

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.