MAAS

  1. Bug #1789932
  2. Comment #0

Comment 0 for bug 1789932

Revision history for this message
Andres Rodriguez (andreserl) wrote : [2.3] use_peer_proxy doesn't prompt maas-proxy to be restart

I recently changed the CI tests so that we test the proxy configuration a bit differently. before, we were simply using an upstream proxy. Now, we are using it as a peer proxy.

THe CI tests do this:

1. configure http_proxy with the external proxy
2. configure use_peer_proxy

While the CI correctly does this, and the maas-proxy.conf file are updated correctly, I noticed that maas-proxy is not being restarted. The reason I noticed is because machines, while they commissioned just fine, they failed to install the required tools because they were unable to reach the archive.

To debug, I logged into the MAAS server, setup itself as a proxy for APT and I did:

1. sudo apt-get update -> it didn't work
2. sudo service maas-proxy restart
3. sudo apt-get update -> it worked.

So that confirms that after /var/lib/maas/maas-proxy.conf was updated, the service was never really restarted.

This is causing consistent CI failures.

NOTE: this does NOT happen in 2.4 or 2.5.