ERROR cannot specify both legacy proxy values and juju proxy values
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Undecided
|
Unassigned |
Bug Description
I'm trying a deploy behind a proxy, and I need for all services to honor that proxy setting: juju itself, the charms, apt, even snaps.
Looking at juju bootstrap --help | proxy, I see a ton of proxy settings:
apt-ftp-proxy:
apt-http-proxy:
apt-https-proxy:
apt-no-proxy:
ftp-proxy:
http-proxy:
https-proxy:
juju-ftp-proxy:
juju-http-proxy:
juju-https-proxy:
juju-no-proxy:
no-proxy:
snap-http-proxy:
snap-https-proxy:
snap-store-proxy:
So I create a config.yaml file with this:
apt-http-proxy: "http://
apt-https-proxy: "http://
apt-no-proxy: "127.0.
juju-http-proxy: "http://
juju-https-proxy: "http://
juju-no-proxy: "127.0.
http-proxy: "http://
https-proxy: "http://
no-proxy: "127.0.
snap-http-proxy: "http://
snap-https-proxy: "http://
When I bootstrap with that, however, juju complains that I'm mixing juju proxy settings with legacy settings:
$ juju bootstrap maas --config juju-bootstrap-
ERROR cannot specify both legacy proxy values and juju proxy values
But it doesn't tell me which ones are the legacy ones. The bootstrap --help command doesn't have the word "legacy" in its output.
Agreed, the error message is unhelpful. Especially when the docs I've seen make not mention of legacy proxy values.
http-proxy, https-proxy and ftp-proxy are considered legacy proxy settings per the error message. You should not use them at the same time as juju-http-proxy, juju-https-proxy, or juju-ftp-proxy.