deployed container in maas provider does not honor maas proxy settings

[Nobuto Murata]

In maas provider, deployed physical nodes will have apt proxy settings as the maas-proxy in maas or value specified in `maas profile maas get-config name=http_proxy`. However containers created by juju in maas provider will have empty value for apt proxy by default.

Containers created by juju should have the same value with physical nodes by default in the same maas provider unless apt-http-proxy is explicitly specified by `juju set-env`.

$ juju get-env | grep http-proxy
<empty>

[physical node]
$ juju run --machine 0 'apt-config dump | grep -i proxy'
Acquire::http::Proxy "http://192.168.88.8:8000/";

[container]
$ juju run --machine 0/lxc/0 'apt-config dump | grep -i proxy'
<empty>

[Nobuto Murata (nobuto)]

Forgot to mention that I checked it with maas 1.9.0+bzr4533-0ubuntu1 and juju-core 1.25.3-trusty-amd64.

[Richard Harding (rharding)]

For now you have to set the config on the models to be respected. Some notes on the model config work here and the apt-http-proxy settings.

https://jujucharms.com/docs/2.0/temp-release-notes#shared-model-config

We do want to pull those from provisioned machines in MAAS but that will not be completed until a later release.

[Anastasia (anastasia-macmood)]

I think this is a duplicate of bug # 1490480. Marking it as such.