Google ubuntu mirror issues

[mrj]

Hello, I'm having an issue updating apt on a server. I couldn't find any information about the google mirror, and I tried using the ubuntu sources directly but they (reasonably) seem to be blocked. So I'm unable to update or install anything.

$ sudo apt update
Hit:1 https://packages.cloud.google.com/apt google-cloud-ops-agent-jammy-2 InRelease
Hit:2 https://download.docker.com/linux/ubuntu jammy InRelease
Ign:3 http://us-east5-a.gce.clouds.archive.ubuntu.com/ubuntu jammy InRelease
Ign:4 http://us-east5-a.gce.clouds.archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:5 http://us-east5-a.gce.clouds.archive.ubuntu.com/ubuntu jammy-backports InRelease
Err:6 http://us-east5-a.gce.clouds.archive.ubuntu.com/ubuntu jammy Release
404 Not Found [IP: 91.189.91.39 80]
Err:7 http://us-east5-a.gce.clouds.archive.ubuntu.com/ubuntu jammy-updates Release
404 Not Found [IP: 91.189.91.39 80]
Err:8 http://us-east5-a.gce.clouds.archive.ubuntu.com/ubuntu jammy-backports Release
404 Not Found [IP: 91.189.91.39 80]
Hit:9 http://security.ubuntu.com/ubuntu jammy-security InRelease
Reading package lists... Done
E: The repository 'http://us-east5-a.gce.clouds.archive.ubuntu.com/ubuntu jammy Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://us-east5-a.gce.clouds.archive.ubuntu.com/ubuntu jammy-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://us-east5-a.gce.clouds.archive.ubuntu.com/ubuntu jammy-backports Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Ubuntu Jammy is the LTS which is still supported so I'm not sure why the release is not found?

From the server this returns nothing:
$ curl -s http://us-east5-a.gce.clouds.archive.ubuntu.com/ubuntu/dists/ | grep jammy
$

But from the outside:
$ curl -s http://us-east5-a.gce.clouds.archive.ubuntu.com/ubuntu/dists/ | grep jammy
<tr><td valign="top"><img src="/icons/folder.gif" alt="[DIR]"></td><td><a href="jammy-backports/">jammy-backports/</a></td><td align="right">2024-06-07 09:34 </td><td align="right"> - </td></tr>
<tr><td valign="top"><img src="/icons/folder.gif" alt="[DIR]"></td><td><a href="jammy-proposed/">jammy-proposed/</a></td><td align="right">2024-06-12 14:25 </td><td align="right"> - </td></tr>
<tr><td valign="top"><img src="/icons/folder.gif" alt="[DIR]"></td><td><a href="jammy-security/">jammy-security/</a></td><td align="right">2024-06-12 14:38 </td><td align="right"> - </td></tr>
<tr><td valign="top"><img src="/icons/folder.gif" alt="[DIR]"></td><td><a href="jammy-updates/">jammy-updates/</a></td><td align="right">2024-06-12 14:24 </td><td align="right"> - </td></tr>
<tr><td valign="top"><img src="/icons/folder.gif" alt="[DIR]"></td><td><a href="jammy/">jammy/</a></td><td align="right">2022-04-21 17:16 </td><td align="right"> - </td></tr>

Any help or pointers would be appreciated. Thanks!

Mike Johnson

[juanjfdez]

Good Morning Mike, I noticed the exact same thing on all my ubuntu servers early yesterday or very late the night before and they are either located on premises or on other public clouds and all of them the apt update script trigger that same error of not finding the Release File for all 3 repos named jammy , jammy-updates and jammy-security.

By late last night it was apparently corrected by the Ubuntu team I guess since apt update went flawless on all of my servers. Normally apt GET or HIT the InRelease file per se instead of the Release file, I guess none was present when it triggered that error. I think they are both the same type of file with the same function and the only difference is that the inRelease is signed in-ine while the Release file has a detached OpenPGP signature.

I just ran my apt update script across all my servers and on both Ubuntu and Debian servers it went flawless so I guess it is all good now. nothing to do with GCP infra or ubuntu mirrors per se.

Cheers

JJ