Galaxy.ansible.com currently down (500 errors)

Get Help
1

Hi guys,

There seem to be a problem during collections install from galaxy.ansible.com.

ERROR! Error when getting collection version metadata for community.library_inventory_filtering_v1:1.1.5 from release_galaxy (https://galaxy.ansible.com/api/) (HTTP Code: 500, Message: Internal Server Error Code: Unknown)

Also, the UI Search (galaxy.ansible.com) is failing with HTTP Error 500.

Is this known?

image
image2230Ă—408 26.7 KB

13 Likes
Ansible Galaxy Down
Galaxy does not handle errors (like 500) from the backend
2

I noticed this earlier in CI this morning, quite a few jobs are failing because of this. No idea whether anyone from RH already knows though…

3

Experiencing same error here, seems like the collections are having issue

4

facing same issue on 4:30PM Beijing time . no issue when launch ansible job on 10:30AM Beijing time .

5

The UI also has the same 500 errors, but apparently doesn’t handle these errors well, and instead claims that things don’t exist, or seems to be loading forever. (I’ll create a separate thread for this to report it.)

Edit: Galaxy does not handle errors (like 500) from the backend

6

Can confirm, ansible-galaxy collection install in GitHub Actions fails with 500s as well.
Fingers crossed, someone can fix this without too much effort. But I would understand, if they only started to work on it Monday morning.

7

Hopeful it will be fixed before Monday morning.

8

Still getting a 500

9

If you are working in an environment without internet access, you can still use Ansible collections by downloading and packaging them in advance, then installing them locally.

First, create two directories: one for cloning collection repositories and one for storing offline packages.

mkdir -p collections_offline/
mkdir -p collections_repos/

Clone the collection source code from GitHub.

cd collections_repos/
git clone https://github.com/ansible-collections/community.general
cd community.general

Build the collection package using Ansible Galaxy. This will generate a versioned .tar.gz file.

ansible-galaxy collection build

Move the generated archive to the offline collections directory.

mv community-general-12.3.0.tar.gz ../../collections_offline

Then install the collections

ansible-galaxy collection install \
  ./collections_offline/*.tar.gz \
  -p collections

To make Ansible use locally installed collections, add the following setting to your ansible.cfg file:

collections_paths = collections

and rename your requirements.yml to explicitly force it not to talk to Galaxy

3 Likes
10

What if we have some collection installed online and some offline, how we deal with that situation? Do you have any setup like that? BTW I think the collections_paths can be absolute path right and in that path we can have multiple collections installed.

11

Thanks for reporting this. I’ve ask the Galaxy team to take a look at report back here.

I’ve created a banner topic for the Forum.

Please keep the discussion useful, ie “I see this too” or “let me know when it’s fixed” don’t move help the discussion.

12 Likes
17

Can you fix the banner? It says ansible.galaxy.com when it is galaxy.ansible.com, it made me think the website was down as well as the link didn’t work.

5 Likes
18

(post deleted by author)

19

I don’t know if it helps the investigation. But I will say that yesterday I couldn’t even login to Ansible galaxy from the UI (I would get 500 error).

Today it is working, but as you know getting collection metadata for example is down for me.(and CI fails)

20

@whitfiea Thanks for pointing that out, I’ve corrected the banner

1 Like
21

To bypass the problem, you can switch to git, e.g.

  - name: signalfx.splunk_otel_collector

↓

  - name: https://github.com/signalfx/splunk-otel-collector.git#/deployments/ansible/
    type: git

or

  - name: community.zabbix
    version: 4.1.1

↓

  - name: https://github.com/ansible-collections/community.zabbix.git
    type: git
    version: 4.1.1
13 Likes