ERROR cannot specify both legacy proxy values and juju proxy values

Bug #1888862 reported by Andreas Hasenack
12
This bug affects 2 people
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://10.96.0.10:8000/"
apt-https-proxy: "http://10.96.0.10:8000/"
apt-no-proxy: "127.0.0.1,localdomain,.localdomain,scapestack,.scapestack,10.96.0.10,10.96.0.1,squid.internal,.internal,internal"

juju-http-proxy: "http://10.96.0.10:8000/"
juju-https-proxy: "http://10.96.0.10:8000/"
juju-no-proxy: "127.0.0.1,localdomain,.localdomain,scapestack,.scapestack,10.96.0.10,10.96.0.1,squid.internal,.internal,internal"

http-proxy: "http://10.96.0.10:8000/"
https-proxy: "http://10.96.0.10:8000/"
no-proxy: "127.0.0.1,localdomain,.localdomain,scapestack,.scapestack,10.96.0.10,10.96.0.1,squid.internal,.internal,internal"

snap-http-proxy: "http://10.96.0.10:8000/"
snap-https-proxy: "http://10.96.0.10:8000/"

When I bootstrap with that, however, juju complains that I'm mixing juju proxy settings with legacy settings:
$ juju bootstrap maas --config juju-bootstrap-config.yaml --to mino.scapestack
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.

Tags: usability
Revision history for this message
Heather Lanigan (hmlanigan) wrote :

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.

tags: added: usability
Changed in juju:
status: New → Triaged
Revision history for this message
Moises Emilio Benzan Mora (moisesbenzan) wrote :

If you try to unset the `http-proxy` and the other legacy variables after setting them, JUJU will complain and not allow you to set the `juju-*` proxy variables.

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1888862] Re: ERROR cannot specify both legacy proxy values and juju proxy values

are you setting them to "" or are you using "juju model-config --reset
http-proxy" ? The latter is the way to get them to be considered not set at
all.

On Fri, Oct 1, 2021 at 12:00 PM Moises Emilio Benzan Mora <
<email address hidden>> wrote:

> If you try to unset the `http-proxy` and the other legacy variables
> after setting them, JUJU will complain and not allow you to set the
> `juju-*` proxy variables.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1888862
>
> Title:
> ERROR cannot specify both legacy proxy values and juju proxy values
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1888862/+subscriptions
>
>

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.