Still having problems with ansible-galaxy

[aleprovencio]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us what version of Renovate you run.

renovate/renovate:37.52

If you're self-hosting Renovate, select which platform you are using.

Gitea or Forgejo

Was this something which used to work for you, and then stopped?

I am trying to get this working for the first time

Describe the problem

Hi,
I've seem that there were already fixes for this before, but for me renovate still fails to fetch some ansible-galaxy packages.

I'm actually having problems with the author.package notation, where packages that have a full github source url are working fine.

Relevant debug logs

Logs

2023-11-10T17:45:47.163076798Z time="2023-11-10T14:45:47-03:00" level=info msg="DEBUG: Failed to look up galaxy package grog.package (repository=aleprovencio/infra-test, ackageFile=galaxy-requirements.yml, dependency=grog.package)" channel=stdout iteration=0 job.command=renovate job.position=0 job.schedule="*/5 * * * *"

2023-11-10T17:45:47.405491087Z time="2023-11-10T14:45:47-03:00" level=info msg="DEBUG: Datasource unknown error (repository=aleprovencio/infra-test)" channel=stdout iteration=0 job.command=renovate job.position=0 job.schedule="*/5 * * * *"

Have you created a minimal reproduction repository?

https://github.com/aleprovencio/renovate-ansible-galaxy-reprod

[github-actions[bot]]

Hi there,

This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions.

No logs at all

If you haven't posted any log yet, we need you to find and copy/paste the log into the issue template.

Finding logs on hosted app

Select me to read instructions

If you use the Renovate app (GitHub):

1. Go to the affected PR, and search for "View repository job log here"
2. Select the link to go to the "Mend Renovate Dashboard" and log in
3. You are now in the correct repository log overview screen
4. Copy/paste the correct log
5. Follow the steps in the formatting your logs section

Finding logs when self-hosting

Select me to read instructions

If you're running self-hosted, run with LOG_LEVEL=debug in your environment variables and search for whatever dependency/branch/PR that is causing the problem.

Insufficient logs

Select me to read instructions

If you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section.

Formatting your logs

Select me to read instructions

Please put your logs in a <details> and <summary> element like this:

<details><summary>Select me to see logs</summary>

```
Copy/paste your logs here, between the starting and ending backticks
```

</details>

Good luck,

The Renovate team

[aleprovencio]

Sorry, somehow the logs didn't make thru the first time

[secustor]

Have you tried capitalizing grog. Seems like there are differences between the Galaxy NG and the old Galaxy registry.

https://galaxy.ansible.com/ui/standalone/roles/GROG/package/
https://old-galaxy.ansible.com/grog/package

[rxbn]

I am seeing the same issue, but also with "geerlingguy.pip", where there seems to be no capitalization in the package name.

[aleprovencio]

Yeah, unfortunately this is not the case, not even for grog.package...but thanks anyways

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this.

To get started, please read our guide on creating a minimal reproduction.

We may close the discussion if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment.

Good luck,

The Renovate team

[aleprovencio]

done :)

[secustor]

#25712