Problem with APT proxy

[bjornrun]

Some machines get this error while commissioning:

Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package lldpd

When going into rescue mode and manually doing apt update:

sudo apt update
Err:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Connection failed [IP: 10.8.8.183 8000]
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-security InRelease
Hit:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease

It seems to be a random problem with the APT proxy in MAAS.
If I switch to an external proxy (standard HTTP proxy), it just works.
How can this be debugged?

[erickeller]

we had similar issue preventing commission of new nodes.
The error was related to the squid proxy on the maas node. Yet the error was a bit different:

Err:4 http://archive.ubuntu.com/ubuntu focal InRelease
Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)

Cleaning up the proxy cache on the maas node did solve the issue.

sudo mv /var/spool/maas-proxy /var/spool/maas-proxy.old
sudo mkdir -p /var/spool/maas-proxy
sudo chown -R proxy:proxy /var/spool/maas-proxy
sudo chmod -R 0750  /var/spool/maas-proxy

There is maybe a better solution to clean up the squid cache.

There is still some ongoing discussion with the MAAS support team how to detect these and maybe autoclean the squid proxy after a while.

[billwear]

@bjornrun, did the suggested solution above help?

[ludww]

I ran into this issue after upgrading our cluster and clearing the cache worked for me as well followed by sudo systemctl restart maas-proxy.