I added another container but the result was the same, the container is created and is running but juju agent isn't installed.
I tried again with other server without VLANs (the other one has 7 VLANs assigned) and I was able to create a container.
~$ juju machines
MACHINE STATE DNS INS-ID SERIES AZ
0 started 10.15.1.2 4y3h7p xenial rack01
0/lxd/3 pending juju-ef10a4-0-lxd-3 xenial
2 started 192.168.2.106 4y3h7q xenial rack02
2/lxd/0 started 192.168.2.3 juju-ef10a4-2-lxd-0 xenial
Hi Tim,
your new binaries propagate the no_proxy value correctly.
~$ sudo -E lxc config show 10.52.18. 78:3128 10.52.18. 78:3128 proxy_ignore_ hosts: 10.52.18. 2,127.0. 0.1,192. 168.2.1, 192.168. 2.2,::1, localhost
config:
core.proxy_http: http://
core.proxy_https: http://
core.
I added another container but the result was the same, the container is created and is running but juju agent isn't installed.
I tried again with other server without VLANs (the other one has 7 VLANs assigned) and I was able to create a container.
~$ juju machines
MACHINE STATE DNS INS-ID SERIES AZ
0 started 10.15.1.2 4y3h7p xenial rack01
0/lxd/3 pending juju-ef10a4-0-lxd-3 xenial
2 started 192.168.2.106 4y3h7q xenial rack02
2/lxd/0 started 192.168.2.3 juju-ef10a4-2-lxd-0 xenial
For my point of view the bug is fixed.
Thanks