http_proxy and no_proxy not filtered from config
Bug #1724338 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
2.2 |
Fix Released
|
High
|
John A Meinel | ||
2.3 |
Fix Released
|
High
|
John A Meinel |
Bug Description
A *very* common mistake that people do when trying to interact with juju and proxies it something like:
juju bootstrap --model-default http_proxy=XXX --model-default no_proxy=YYY
however, the actual values you have to set are:
juju bootstrap --model-default http-proxy=
We should look for "http_proxy" and either provide a warning that "you really should use http-proxy" or just accept the value instead.
Changed in juju: | |
status: | In Progress → Fix Committed |
status: | Fix Committed → In Progress |
Changed in juju: | |
milestone: | 2.3-beta2 → none |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It turns out that all providers have to directly validate "unknown" fields. Most do it naturally because that is where provider-specific configuration lives.
However, LXD didn't have any provider-specific configuration, so was missing the check.
I also updated our validation to do a simple spellcheck for getting "_" mixed up with "-".