Why am I getting "Authentication failed" while running do-release-upgrade from 19.10 to 20.04 LTS with configured squid-deb-proxy client?

I'm running squid-deb-proxy server in my local network. It works well for all package downloads while running all APT commands. It is configured for all possible known URLs of the mirrors including old-releases. The Ubuntu 19.10 client has installed client side - the squid-deb-proxy-client package.

$ dpkg -l squid-deb-proxy-client | tail -n1
ii squid-deb-proxy-client 0.8.14+nmu2 all automatic proxy discovery for APT based on Avahi
$ sudo apt update
Hit:1 eoan InRelease
Hit:2 eoan-updates InRelease
Hit:3 eoan-backports InRelease
Hit:4 eoan-security InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

But when I try to start upgrade process to get 20.04 LTS - using sudo do-release-upgrade in the terminal I got the following error message:

$ sudo do-release-upgrade
Checking for a new Ubuntu release
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
Get:1 Upgrade tool signature [1 554 B]
Get:2 Upgrade tool [1 342 kB]
Fetched 1 343 kB in 0s (0 B/s)
authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg'
Authentication failed
Authenticating the upgrade failed. There may be a problem with the network or with the server. 

I do not see anything special in the logs on squid-deb-proxy server side:

==> /var/log/squid-deb-proxy/access.log <==
1595069772.862 212 192.168.3.47 TCP_MISS/200 3349 CONNECT changelogs.ubuntu.com:443 - HIER_DIRECT/91.189.95.15 -
1595069774.726 2 192.168.3.47 TCP_MEM_HIT/200 1950 GET - HIER_NONE/- application/x-gzip
1595069775.410 681 192.168.3.47 TCP_HIT/200 1342082 GET - HIER_NONE/- application/x-gzip

How should I fix the problem with Authentication failed to run the upgrade through proxy server normally? I do not want to switch proxy server (or exclude its configuration from the client) off to fix the problem.

---

Notes:

1. For possible close-voters: the same happening when I try to upgrade 18.04 LTS to 20.04 LTS with sudo do-release-upgrade -d.
2. I have reported bug 1888058 to launchpad.
3. Removing squid-deb-proxy-client deb-package and specifying proxy by Acquire::http::Proxy ""; in /etc/apt/apt.conf does not change anything.

3

2 Answers

This problem has nothing to do with your squid proxy. It is not able to match the downloaded file 'focal.tar.gz' with it's GPG Key in file 'focal.tar.gz.gpg'.

This problem is solved in:

Where, as Hiren suggested, you have to replace with following in

/etc/apt/sources.list

But do take a backup of this file before replacing.

deb focal main restricted universe multiverse
deb-src focal main restricted universe multiverse
deb focal-updates main restricted universe multiverse
deb-src focal-updates main restricted universe multiverse
deb focal-security main restricted universe multiverse
deb-src focal-security main restricted universe multiverse
deb focal-backports main restricted universe multiverse
deb-src focal-backports main restricted universe multiverse
deb focal partner
deb-src focal partner

Then,

sudo apt-get install --reinstall ubuntu-keyring

0

The problem here was caused by the fact that my proxy had old version of the installer files.

So I fixed the issue by triggering manual cache update by the commands on client:

cd /tmp
http_proxy= wget --no-cache -c
http_proxy= wget -c 

and on server:

sudo service squid3 restart
sudo service squid-deb-proxy restart

And then upgrade ran well.

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password Submit

Post as a guest

Post Your Answer Discard

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy