Osgeo repository hiccup: Bad Gateway (502)

[danieleromagnoli]

Hi all,

in the last couple of days, sometime, I get some local build failures due to a bad gateway error returned by osgeo repository.

This morning, a GeoServer PR is failing on most part of the checks due to the same error:

For example:

Error: 9,364 [ERROR] Failed to read artifact descriptor for org.geotools:gt-imagepyramid:jar:35-SNAPSHOT

Error: 9,364 [ERROR] 	Caused by: The following artifacts could not be resolved: org.geotools:gt-imagepyramid:pom:35-SNAPSHOT (absent): Could not transfer artifact org.geotools:gt-imagepyramid:pom:35-SNAPSHOT from/to osgeo-snapshots (
): status code: 502, reason phrase: Bad Gateway (502)

Error: 9,364 [ERROR] Failed to read artifact descriptor for org.geotools:gt-iau-wkt:jar:35-SNAPSHOT

Error: 9,364 [ERROR] 	Caused by: The following artifacts could not be resolved: org.geotools:gt-iau-wkt:pom:35-SNAPSHOT (absent): Could not transfer artifact org.geotools:gt-iau-wkt:pom:35-SNAPSHOT from/to osgeo-snapshots (https://repo.osgeo.org/repository/snapshot/): status code: 502, reason phrase: Bad Gateway (502)

Do you have any idea about that?

I see this message being posted a few days ago:

Repo.osgeo.org needs to be moved to osgeo7

As part of the OSUOSL data center migration, we need to decommission all old servers we will not be taking with us. osgeo3 has been deemed too old to keep. As such we are going to move repo.osgeo.org (our nexus instance) to osgeo7. I have the item ticketed here - https://trac.osgeo.org/osgeo/ticket/3468 The main thing I will need from your group is during the migration if we can pause build.geoserver.org which I think is the only service that continually pushes to repo.osgeo.org Given that …

Could that be related?

Please let me know if you have any clue.

Regards, Daniele