| 2017-07-04 16:10:09 |
Julen Larrucea |
description |
On Ubuntu 17.04
MaaS 2.2.0~rc1+bzr5922-0ubuntu2
Setting up a custom http-proxy is used for '/etc/apt.conf.d/90cloud-init-aptproxy' on the targets while commissioning. So far so good.
Unfortunately, the commissioning of a plain and default Ubuntu node also involves some fancy calls to
i.e. 'https://search.apps.ubuntu.com/api/v1/snaps/metadata' or 'ntp.ubuntu.com'.
These calls will not likely success, because, as the $http_proxy variable on the controller already knows, ... we are behind a proxy.
Why not to include the http_proxy as a global environment variable? |
On Ubuntu 17.04
MaaS 2.2.0~rc1+bzr5922-0ubuntu2
Setting up a custom http-proxy is used for '/etc/apt.conf.d/90cloud-init-aptproxy' on the targets while commissioning. So far so good.
Unfortunately, the commissioning of a plain and default Ubuntu node also involves some fancy calls to
i.e. 'https://search.apps.ubuntu.com/api/v1/snaps/metadata' or 'ntp.ubuntu.com'.
These calls will not likely success, because, as the $http_proxy variable on the controller already knows, ... we are behind a proxy.
Why not to include the http_proxy as a global environment variable on the target nodes? |
|
