2.0beta10: http proxy not used when deploying to lxd with MAAS

Bug #1596081 reported by Andreas Hasenack
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
New
Undecided
Unassigned

Bug Description

juju 2.0beta10

Hi,

I have this cloud defined:
$ juju show-cloud local:vmwarestack-xenial
defined: local
type: maas
auth-types: [oauth1]
endpoint: http://10.245.200.27/MAAS
config:
  bootstrap-timeout: 900
  default-series: xenial
  http-proxy: http://10.245.200.27:8000/
  https-proxy: http://10.245.200.27:8000/
  no-proxy: 127.0.0.1,localhost,169.254.169.254,10.245.200.27

I can bootstrap and deploy nodes (tried ubuntu and mysql). Each node gets the proxy set in ~ubuntu/.juju-proxy. So that works.

What isn't working is deploying to an lxd inside a node. Like "juju add-unit ubuntu --to lxd:0", or just "juju deploy foo --to lxd:0":
machine-0: 2016-06-24 20:01:50 WARNING juju.provisioner broker.go:92 no DNS settings found, discovering the host settings
machine-0: 2016-06-24 20:02:03 ERROR juju.worker.diskmanager lsblk.go:116 error checking if "fd0" is in use: open /dev/fd0: no such device or address
machine-0: 2016-06-24 20:02:11 ERROR juju.provisioner provisioner_task.go:687 cannot start instance for machine "0/lxd/0": failed to ensure LXD image: unable to get LXD image for ubuntu-xenial: Get https://cloud-images.ubuntu.com/releases/streams/v1/index.json: Unable to connect to: cloud-images.ubuntu.com:443

It's not using the proxy. The same was happening with beta9, and I don't know about previous versions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.