MAAS configured apt proxy gets in the way of Juju configured one

[Mario Splivalo]

When one uses juju with maas provider to deploy machines, maas will put apt-proxy configuration in /etc/apt/apt.conf.d/90curtin-aptproxy.

If one configures juju environment with apt-proxy (inside environment.yaml, for instance), juju will create /etc/apt/apt.conf.d/42-juju-proxy-settings. But, that one will get overridden by 90curtin-aptproxy.

I'm not sure what is the best solution to this, or is this is even a Maas bug. One solution would be for maas to create 40curtin-aptproxy file so that juju can override it if needed.

Or juju provider could, realizing it's deploying on maas, overwrite 90curtin-aptproxy.

[Andres Rodriguez (andreserl)]

This is probably something that MAAS won't fix. MAAS provides a proxy that would work with or without juju, and if Juju is using MAAS as a provider, JUju should be getting the proxy from MAAS.

[Mario Splivalo (mariosplivalo)]

Hm, so you're suggesting that juju overwrite the maas-supplied Apt Configuration for http proxy?

The scenario is, for instance, that the environment already has apt-cacher-ng configured on the network, and I want all of my machines to use that proxy (because, for instance, I have non-MAAS/Juju machines that are already using it and I want to avoid re-downloading of the packages).

Is there a (simple) way to change what MAAS will be providing as Apt Http Proxy?

[Christian Reis (kiko)]

Mario, you can remove the MAAS proxy information from the settings page which should stop it from trying to trying to set up proxies from the nodes. Can you verify whether that works?

[Mario Splivalo (mariosplivalo)]

I just verified - I deployed maas 1.7.5+bzr3369-0ubuntu1~trusty1 from maas stable ppa. It installed maas-proxy.
I haven't configured http proxy in maas.

When I deploy new nodes I get maas-proxy IP address in /etc/apt/apt.conf.d/90curtin-aptproxy.
If I then configure http proxy in MAAS (under "Network Configuration" -> "Proxy for HTTP and HTTPS traffic"), and deploy another node, that deployed node has http proxy I just configured in 90curtin-aptproxy.

So, in that manner I can control what to put as Apt::Http::Proxy in apt configuration, via MAAS. However, I can not 'disable' it (and let juju, for instance, take care of it).

Also, as I'm running apt-cacher-ng as an apt proxy (which for me behaves way better than squid), MAAS won't be able to download new boot images, as those don't reside in apt-cacher-ng.

There should definitely be an option push separate Apt::Http::Proxy configuration to the deployed nodes. That way user can choose not to let MAAS push that info altogether.