chaining nexus fails with collections with many published versions

[msegura501]

• What are you trying to do?

We have a setup where one air-gapped nexus is talking to another nexus. This other nexus finally accesses galaxy.ansible.com.

Both nexus have the l3ender/nexus-repository-ansiblegalaxy.

When we try to fetch the community.general collection through the air gapped nexus, it fails with :

ansible-galaxy collection install -s  https://nexus.damien.nubo.dgfip/repository/ansible_galaxy_registry -vvvvvvv  -f  --no-cache  -c  community.general:7.4.0 
ansible-galaxy [core 2.18.0]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/msegura-devillecha01/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/msegura-devillecha01/.pyenv/versions/3.11.0/lib/python3.11/site-packages/ansible
  ansible collection location = /home/msegura-devillecha01/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/msegura-devillecha01/.pyenv/versions/3.11.0/bin/ansible-galaxy
  python version = 3.11.0 (main, Sep 19 2023, 16:47:20) [GCC 9.4.0] (/home/msegura-devillecha01/.pyenv/versions/3.11.0/bin/python3.11)
  jinja version = 3.1.3
  libyaml = True
Using /etc/ansible/ansible.cfg as config file
Starting galaxy collection install process
Loading collection community.general from /home/msegura-devillecha01/.ansible/collections/ansible_collections/community/general
Found installed collection community.general:7.4.0 at '/home/msegura-devillecha01/.ansible/collections/ansible_collections/community/general'
Loading collection openstack.cloud from /home/msegura-devillecha01/.ansible/collections/ansible_collections/openstack/cloud
Found installed collection openstack.cloud:2.1.0 at '/home/msegura-devillecha01/.ansible/collections/ansible_collections/openstack/cloud'
Process install dependency map
Initial connection to galaxy_server: https://nexus.damien.nubo.dgfip/repository/ansible_galaxy_registry
Opened /home/msegura-devillecha01/.ansible/galaxy_token
Calling Galaxy at https://nexus.damien.nubo.dgfip/repository/ansible_galaxy_registry
Calling Galaxy at https://nexus.damien.nubo.dgfip/repository/ansible_galaxy_registry/api
Found API version 'v3, pulp-v3, v1' with Galaxy server cmd_arg (https://nexus.damien.nubo.dgfip/repository/ansible_galaxy_registry/api)
Calling Galaxy at https://nexus.damien.nubo.dgfip/repository/ansible_galaxy_registry/api/v3/collections/community/general/versions/?limit=100
Calling Galaxy at https://nexus.damien.nubo.dgfip/repository/ansible_galaxy_registry/repository/ansible_galaxy_v3/api/v3/plugin/ansible/content/published/collections/index/community/general/versions/?limit=100&offset=100
ERROR! Error when getting available collection versions for community.general from cmd_arg (https://nexus.damien.nubo.dgfip/repository/ansible_galaxy_registry/api) (HTTP Code: 404, Message: Not Found Code: Unknown)

However if we point ansible-galaxy to the nexus accessing galaxy.ansible.com directly without intermediaries, it works.

The problem seems to affect collections with a large number of published versions.

• What feature or behavior is this required for?

This feature is useful for airtight environment (like production environments) where ansible is meant to deploy something.

community.general is routinely used with ansible-core.