I tried to deploy a charm to nodes managed by maas in environment that is behind a firewall (like 1ss). I set http/s-proxy and no-proxy but juju deploy from charm store fails. I was able to bootstrap with the yaml below but deploying charm from charmstore fails, I was expecting that http/s-proxy and no-proxy will take care of that. I would rather not punch a hole in the firewall to get to the charmstore.
==== environment.yaml ====
maas:
type: maas
# maas-server specifies the location of the MAAS server. It must
# specify the base path.
#
maas-server: 'http://10.229.32.22/MAAS/'
# maas-oauth holds the OAuth credentials from MAAS.
#
maas-oauth: 'L3...removed for sanity..pyZ'
http-proxy: http://squid.internal:3128
https-proxy: http://squid.internal:3128
no-proxy: localhost,127.0.,10.229.,10.229.32.22,.local
# maas-server bootstrap ssh connection options
#
# bootstrap-timeout time to wait contacting a state server, in seconds.
bootstrap-timeout: 2800
admin-secret: 'ubuntu'
========
==== juju status ====
environment: maas
machines:
"0":
agent-state: started
agent-version: 1.24.5
dns-name: ms10-02-avaton.1ss
instance-id: /MAAS/api/1.0/nodes/node-4d1d8302-5b19-11e5-95db-00163ec335e8/
series: trusty
hardware: arch=amd64 cpu-cores=8 mem=32768M tags=myhardware
state-server-member-status: has-vote
services: {}
=========
==== juju deploy mysql =====
ubuntu@manjoubuntu:~$ sudo juju deploy mysql --constraints tags=myhardware --debug2015-09-15 20:47:12 INFO juju.cmd supercommand.go:37 running juju [1.24.5-trusty-amd64 gc]
2015-09-15 20:47:12 DEBUG juju.api api.go:168 trying cached API connection settings - endpoints [10.229.65.102:17070]
2015-09-15 20:47:12 INFO juju.api api.go:280 connecting to API addresses: [10.229.65.102:17070]
2015-09-15 20:47:12 INFO juju.api apiclient.go:331 dialing "wss://10.229.65.102:17070/environment/6b0f6ece-333f-4197-8d79-09f4d530a0b9/api"
2015-09-15 20:47:12 INFO juju.api apiclient.go:263 connection established to "wss://10.229.65.102:17070/environment/6b0f6ece-333f-4197-8d79-09f4d530a0b9/api"
2015-09-15 20:47:12 DEBUG juju.api api.go:482 API hostnames changed from [ms10-02-myhardware.1ss:17070] to [10.229.65.102:17070 ms10-02-myhardware.1ss:17070] - resolving hostnames
2015-09-15 20:47:12 DEBUG juju.api api.go:513 API addresses unchanged
2015-09-15 20:47:12 DEBUG juju.api api.go:522 cacheChangedAPIInfo: serverUUID="6b0f6ece-333f-4197-8d79-09f4d530a0b9"
2015-09-15 20:47:12 DEBUG httpbakery client.go:224 client do GET https://api.jujucharms.com/charmstore/v4/mysql/meta/any?include=id {
2015-09-15 20:49:20 DEBUG httpbakery client.go:226 } -> error &url.Error{Op:"Get", URL:"https://api.jujucharms.com/charmstore/v4/mysql/meta/any?include=id", Err:(*net.OpError)(0xc2101b4380)}
2015-09-15 20:49:20 ERROR juju.cmd supercommand.go:430 cannot resolve charm URL "cs:mysql": cannot get "/mysql/meta/any?include=id": Get https://api.jujucharms.com/charmstore/v4/mysql/meta/any?include=id: dial tcp 162.213.33.121:443: connection timed out
=========
This looks like a client side issue. The HTTPS request that's failing is being made by the client, not the server. Juju's proxy configuration options are for the Juju server and aren't used by the client.
Can you check that http-proxy, https-proxy and no-proxy are correctly set up on the client?