Question

Ubuntu repository problem in London

Posted May 10, 2018 4.9k views
Linux BasicsUbuntu

I getting problem with Ubuntu repository on Ubuntu 16.04 and 18.04 droplets created in London. For droplets created in Frankfurt everything works out of box.

Does anyone experiencing this too?

# apt-get update

Ign:4 http://security.debian.org bionic/updates InRelease
Ign:1 http://lon1.mirrors.digitalocean.com/debian bionic InRelease
Err:6 http://security.debian.org bionic/updates Release
  404  Not Found [IP: 151.101.60.204 80]
Ign:2 http://lon1.mirrors.digitalocean.com/debian bionic-updates InRelease
Ign:3 http://lon1.mirrors.digitalocean.com/debian bionic-backports InRelease
Err:5 http://lon1.mirrors.digitalocean.com/debian bionic Release
  404  Not Found [IP: 5.101.111.50 80]
Err:7 http://lon1.mirrors.digitalocean.com/debian bionic-updates Release
  404  Not Found [IP: 5.101.111.50 80]
Err:8 http://lon1.mirrors.digitalocean.com/debian bionic-backports Release
  404  Not Found [IP: 5.101.111.50 80]
Hit:9 https://repos.sonar.digitalocean.com/apt main InRelease
Reading package lists... Done
E: The repository 'http://security.debian.org bionic/updates Release' does not have 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://mirrors.digitalocean.com/debian bionic 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://mirrors.digitalocean.com/debian bionic-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://mirrors.digitalocean.com/debian bionic-backports Release' does not have 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.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
2 answers

To work around the issue I changed my sources to:

## Note, this file is written by cloud-init on first boot of an instance modifications made here will not 
## survive a re-bundle. if you wish to make changes you can:
## a.) add 'apt_preserve_sources_list: true' to  /etc/cloud/cloud.cfg or do the same in user-data 
## b.) add sources in /etc/apt/sources.list.d 
## c.) make changes to template file /etc/cloud/templates/sources.list.tmpl


# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to newer versions of the distribution.
deb http://mirrors.digitalocean.com/ubuntu/ bionic main restricted
deb-src http://mirrors.digitalocean.com/ubuntu/ bionic main restricted

## Major bug fix updates produced after the final release of the distribution.
deb http://mirrors.digitalocean.com/ubuntu/ bionic-updates main restricted
deb-src http://mirrors.digitalocean.com/ubuntu/ bionic-updates main restricted


## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu team. Also, please note that 
## software in universe WILL NOT receive any review or updates from the Ubuntu security team.
deb http://mirrors.digitalocean.com/ubuntu/ bionic universe
deb-src http://mirrors.digitalocean.com/ubuntu/ bionic universe
deb http://mirrors.digitalocean.com/ubuntu/ bionic-updates universe
deb-src http://mirrors.digitalocean.com/ubuntu/ bionic-updates universe


## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu team, and may not be under a free 
## licence. Please satisfy yourself as to your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu security team.
deb http://mirrors.digitalocean.com/ubuntu/ bionic multiverse
deb-src http://mirrors.digitalocean.com/ubuntu/ bionic multiverse
deb http://mirrors.digitalocean.com/ubuntu/ bionic-updates multiverse
deb-src http://mirrors.digitalocean.com/ubuntu/ bionic-updates multiverse


## N.B. software from this repository may not have been tested as extensively as that contained in the main 
## release, although it includes newer versions of some applications which may provide useful features. Also, 
## please note that software in backports WILL NOT receive any review or updates from the Ubuntu security team.
deb http://mirrors.digitalocean.com/ubuntu/ bionic-backports main restricted universe multiverse
deb-src http://mirrors.digitalocean.com/ubuntu/ bionic-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu bionic-security main restricted
deb-src http://security.ubuntu.com/ubuntu bionic-security main restricted
deb http://security.ubuntu.com/ubuntu bionic-security universe
deb-src http://security.ubuntu.com/ubuntu bionic-security universe
deb http://security.ubuntu.com/ubuntu bionic-security multiverse
deb-src http://security.ubuntu.com/ubuntu bionic-security multiverse

## Uncomment the following two lines to add software from Canonical's 'partner' repository. This software is not 
## part of Ubuntu, but is offered by Canonical and the respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu bionic partner deb-src http://archive.canonical.com/ubuntu bionic 
# partner

I’m having a lot of issues in FrankFurt as well running installs through ansible on freshly created droplets with xenial ?

Same scripts were running perfectly yesterday :/ what’s going on here guys? I thought the premade builds were stable :/ appears they’re really not

  • Looks like the issue on my side was due to ansible seeing apt warnings about custom digitalocean repository lists not being found as errors.

    Managed to find a workaround but still has the fact that these scripts worked until yesterday. What changes were made to the ubuntu images and repo lists ?

Submit an Answer