Installing globus-repo-latest.noarch.rpm causes errors in subsequesnt dnf commands - Rocky Linux 9.4

[Alan Sill]

After the step in the subject line, 

dnf install https://downloads.globus.org/globus-connect-server/stable/installers/repo/rpm/globus-repo-latest.noarch.rpm

any subsequent dnf command produces an error:

Globus Connect Server 5 Stable                                                                                                                                                             1.6 kB/s | 401  B     00:00    

Errors during downloading metadata for repository 'Globus-Connect-Server-5-Stable':

  - Status code: 404 for https://downloads.globus.org/globus-connect-server/stable/rpm/el/9.4/x86_64/repodata/repomd.xml (IP: 18.160.172.40)

Error: Failed to download metadata for repo 'Globus-Connect-Server-5-Stable': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

The only way to recover is to remove the globus -repo package 

dnf remove \*globus\*

Looking in the area https://downloads.globus.org/globus-connect-server/stable/rpm/el/ shows areas for 7, 8, and 9 but not a specific area for any point versions such as 9.4 

Is the globus-repo package broken? Ir has there been a change to the organization of the above area?

[Alan Sill]

I was able to proceed by replacing the $releasever variable in the globus repo with "9" in my case. I suspect this may be due to our site using the LTS versions of Rocly linux where $releasever may be set at the OS level to the specific LTS release we are using. Perhaps there could be a way to handle this by setting the value of is field to the top-level release (9 instead of 9.4 for example) in the repos installed by the globus-repo-latest.noarch.rpm package?

[Michael Link]

Hi Alan,

Do you have something in /etc/dnf/ overriding the `$releasever`
variable? Rocky and the other RH based repos we support have always set
it to the distro's major version.

Mike

On 4/27/2025 10:52 AM, Alan Sill wrote:
> I was able to proceed by replacing the $releasever variable in the
> globus repo with "9" in my case. I suspect this may be due to our site
> using the LTS versions of Rocly linux where $releasever may be set at
> the OS level to the specific LTS release we are using. Perhaps there
> could be a way to handle this by setting the value of is field to the
> top-level release (9 instead of 9.4 for example) in the repos installed
> by the globus-repo-latest.noarch.rpm package?
>
> On Saturday, April 26, 2025 at 11:33:55 PM UTC-5 Alan Sill wrote:
>
> After the step in the subject line,
>
> dnf install https://downloads.globus.org/globus-connect-server/

> stable/installers/repo/rpm/globus-repo-latest.noarch.rpm <https://
> downloads.globus.org/globus-connect-server/stable/installers/repo/
> rpm/globus-repo-latest.noarch.rpm>

>
> any subsequent dnf command produces an error:
>

> /Globus Connect Server 5 Stable
>
>                                                     1.6 kB/s | 401
> B     00:00 /
>
> /Errors during downloading metadata for repository 'Globus-Connect-
> Server-5-Stable':/
>
> /  - Status code: 404 for https://downloads.globus.org/globus-
> connect-server/stable/rpm/el/9.4/x86_64/repodata/repomd.xml
> <https://downloads.globus.org/globus-connect-server/stable/rpm/
> el/9.4/x86_64/repodata/repomd.xml> (IP: 18.160.172.40)/
>
> /Error: Failed to download metadata for repo 'Globus-Connect-

> Server-5-Stable': Cannot download repomd.xml: Cannot download

> repodata/repomd.xml: All mirrors were tried/

>
> The only way to recover is to remove the globus -repo package
>
> dnf remove \*globus\*
>
> Looking in the area https://downloads.globus.org/globus-connect-

> server/stable/rpm/el/ <https://downloads.globus.org/globus-connect-
> server/stable/rpm/el/> shows areas for 7, 8, and 9 but not a