Comment 13 for bug 1681278

Hello,

May be, I forgot to tell you about the Network Configuration in MAAS :
The use of an APT and HTTP/HTTPS proxy Provision nodes to use the built-in HTTP proxy (or user specified proxy) for APT. MAAS also uses the proxy for downloading boot images is enableded
http://user:password@192.168.168.5:10080

From the managed host :

ubuntu@needed-bison:~$ export http_proxy="http://user:password@192.168.168.5:10080"
ubuntu@needed-bison:~$ export https_proxy="http://user:password@192.168.168.5:10080"
ubuntu@needed-bison:~$ wget jujucharms.com --no-check-certificate
--2017-05-03 08:44:24-- http://jujucharms.com/
Connecting to 192.168.168.5:10080... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://jujucharms.com/ [following]
--2017-05-03 08:44:26-- https://jujucharms.com/
Connecting to 192.168.168.5:10080... connected.
WARNING: cannot verify jujucharms.com's certificate, issued by ‘emailAddress=me.com,CN=myproxy,OU=myou,O=myo,L=myloc,ST=myst,C=myc’:
  Unable to locally verify the issuer's authority.
Proxy request sent, awaiting response... 200 OK

On maas server it is still looping on the following steps until it is timed out:

04:47:46 TRACE maas controller.go:792 request 78: GET http://10.137.184.211/MAAS/api/2.0/machines/?agent_name=de797dc2-a8d6-48c1-8716-fc932bcc926b&id=ya7dwr
04:47:46 TRACE maas controller.go:800 response 78: ...

If it helps you.

Thank you