I want to upgrade my Ubuntu 16.04 server to Ubuntu 18.04 and I'm running the following commands to do so;
apt update -y
apt upgrade -y
do-release-upgrade
apt update
command runs fine with the following output;
# apt update -y
Hit:1 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security InRelease
Hit:2 https://esm.ubuntu.com/infra/ubuntu bionic-infra-updates InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
However when running the apt upgrade
command, it returns the following errors;
# apt upgrade -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
*The following packages could receive security updates with UA Infra: ESM service enabled:
libkrb5-3 libgssapi-krb5-2 libk5crypto3 libkrb5support0 libzstd1
Learn more about UA Infra: ESM service for Ubuntu 16.04 at https://ubuntu.com/16-04
Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.
The following packages have been kept back:
libk5crypto3 libkrb5support0
The following packages will be upgraded:
libzstd1
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 esm-infra security update
Need to get 189 kB of archives.
After this operation, 132 kB of additional disk space will be used.
Err:1 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64 libzstd1 amd64 1.3.3+dfsg-2ubuntu1+esm1
401 Unauthorized
E: Failed to fetch https://esm.ubuntu.com/infra/ubuntu/pool/main/libz/libzstd/libzstd1_1.3.3+dfsg-2ubuntu1+esm1_amd64.deb 401 Unauthorized
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
I'm not sure what to do at this point. How can I solve this?
esm.ubuntu.com
form your sources list, since you are upgrading, you don't need extended support.esm.ubuntu.com
in my sources list at all.bionic
instead ofxenial
). 18.04 does not need to be ESM, since it's still in Community Support. This suggests that somebody already tried ado-release-upgrade
that failed. Perhaps the upgrader left the altered sources in place (it happens). You can change the sources back to Xenial.