Comment 1 for bug 1789932

The puzzling thing about this issue is the fact that MAAS always tries to reload the service when it writes out the config (if I'm reading the code correctly in maasserver/proxyconfig.py).

But I just had an idea: what if it's not working because we're using *reload* and not *restart*? (The code has two separate paths depending on whether or not we're running in the snap.)

So, what if it's a bug that occurs because the service is being reloaded and not restated?

If you get a chance, could you repeat your test, and check whether or not the second `apt-get update` works after a *reload* and not a restart?

If it fails with reload and then works with restart, I think we have our answer. It could be that there was a problem with reloading that was fixed with a post-Xenial version of squid.